-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
\IfInstanceExistTF unavailable in 2024-06-01 pre-release 1 #1306
Comments
Sure, but this is a pre-test ;) So it's always possible you have to make minor adjustments in your sources as things get tested. A new dev release is likely before Easter, we are just finishing off some additions and will likely agree on things on Tuesday. |
@muzimuzhi -dev releases are for testing and yes, sometimes they show a breakage that was intorduced by mistake. That doesn't mean that we immediately intoroduce a new release. Please understand that overall making a dev release results in several hours of work for both us and the CTAN folks combined and we have to be careful in managing the limited resources here. |
@FrankMittelbach I totally get this argument. But as developers are encouraged to use |
My take on this is that one can and should have a testsuite set up so that it can use either or latex or latex-dev format. Yes we encourage developers to test against -dev but obviously you also need to test against main because most of your users will be using main andd if something is reported as broken one needs to see what fails with main and how to fix that. So the idea is that a test suite should report success with main and you should regularly run it using -dev and see if this this breaks anything and if so report a problem to us -- or fix your code to work both with current main and -dev aka upcoming main if it is a legitimate change. For example, I run all of the TLC3 sources against -dev usually to ensure that the book is not broken with the next main, but because of the \IfInstanceExistTF issue I had to fall back to "main" at the moment and wait for a new -dev release to appear. The "identical release of latex-dev for each major release" is the latex release without -dev in the name so I'm not what you are asking and yes making another release with a different name introduces the same amount of work ... it is making a release that is the work (and get it through all stages) even though a lot of it is automated. |
Agreed
I asked having some automated test suite in mind running for both |
I guess that's what I feel is happening: you test, there's an issue, you patch round it until the next dev release ... |
sorry, I'm still not getting what you are after. Suppose you have a simple setup:
you wouldn't expect in this case that CTAN keeps 2 releases of main, would you? Now assume your test suite runs both main and -dev tests
What I could envision (and perhaps that is what you are asking) is some flax or config setting that allows you to run your test suite in 3 modes:
but to have yet another full latex distribution as in latex-previous-dev seems overkill to me because that is much better done by not testing -dev for a while (but maybe you didn't mean that). |
Nope, I wouldn't. I am only talking about the point, where
By reading "new kernel code" I mistakenly assumed, that this is already out in As far as I can see, there is actually a new release of Sorry for the noise. |
yes we add a dev 0 very soon after each main (just wait a bit in case we have overlooked something and need a patch release) so usually, dev is ahead of main (and even after a new release of main it is more of less = to main so on this front we are usually ok even in the daves directly after the main release). as a new dev is going to show up real soon* I'm going to close this issue. |
Brief outline of the bug
At the time when 2024-06-01 pre-release 1 was released,
\IfInstanceExist(TF)
were both removed from the new kernel code and latestxtemplate
package. Therefore in current -dev formats,\IfInstanceExist(TF)
are always undefined with or withoutxtemplate
package loaded.This introduced a regression that packages which load
xtemplate
and make use of\IfInstanceExist(TF)
may not work with 2024-06-01 pre-release 1, for instancexeCJK
(CTeX-org/ctex-kit#707).As these commands were already reintroduced to the kernel (41f33bc4 (Re-introduce \IfInstanceExist(TF), 2024-02-15)), a new pre-release would resolve the problem.
Minimal example showing the bug
xtemplate
loaded?\IfInstanceExsitTF
defined?pdflatex
)pdflatex-dev
)Log file (required) and possibly PDF file
latex2e-no-IfInstanceExistTF-in-2024-06-01-pre-release-1.log
The text was updated successfully, but these errors were encountered: