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
Package identification #15
Comments
The problem we have is that
My personal preference is the first option: there was a suggestion on LaTeX-L a while ago to drop |
I guess the easiest option is to use |
I'm also with Philipp on |
Good idea. In time I guess we can think about improving In fact, I reckon we could just use one of the other SVN-keywords packages for our needs and drop the SVN metadata when we're creating a format. It'd be nice to simplify that aspect of the package loading, and I'm sure the dedicated packages do a better job than we do with the string parsing. Hmm.... |
True: I'd go for the svn-multi package, as it's up to date and seems to be well-supported. We'd then only need
with the only issue being
BTW, I've already tested
|
I did a bit of experimenting, and for svn-multi we'd actually do something like
|
I should add that I think this is probably one that can be covered as part of the 'big bang' (provided that happens soon!) |
It occurs to me that using svn-mutli would still leave us open to the danger that someone might do
and get a surprising result. So I think the best fix in the short term is to use a dedicated set of macros that will not conflict with anyone else. |
This fixes issue #15, and also restricts the output to things we use Should be safe as only the team use \GetIdInfo I think (This leaves open the long-term, and a desire to move away from SVN-based approaches, at least on my part!) git-svn-id: svn+ssh://comedy.dante.de/serv/latex-project/svn/experimental/trunk@2478 de43f980-851b-0410-b2f7-c40aca1f87e0
I'm going to close this particular issue here — but we may want to go back to a formal module identification syntax that you've suggested before. Happy to either have it raised as another issue or just to keep it in the back of our minds. |
This fixes issue #15, and also restricts the output to things we use Should be safe as only the team use \GetIdInfo I think (This leaves open the long-term, and a desire to move away from SVN-based approaches, at least on my part!) git-svn-id: http://www.latex-project.org/svnroot/experimental/trunk@2478 de43f980-851b-0410-b2f7-c40aca1f87e0
I guess I agree with Rasmus here:
We've spoken about this before (Joseph had some good ideas at one point), and this is not the first time it has come up.
The text was updated successfully, but these errors were encountered: