I need some advice. I am going to bundle a package of mine (lets say its named foo, currently v2.0a) with two not yet released packages (therefore both v0.1).
I am unsure which version number the “foo bundle” should get. I can think of different approaches:
- Let every package keep its own version number and don't use a version number for the bundle but the release date. But then I'd have to tell CTAN a version like
2012/01/27. Seems odd. And I'd have to keep track of three different version numbers (which is not too big a deal but still…) - Give the whole bundle and every package the same version number, either
2.1(which would be the next number I'd choose forfooif I didn't bundle the packages) or3.0since the bundling seems a large enough step for a new main version number. However, I don't really like the idea giving previously unreleased packages a number like2.1or3.0even if they are part of a bundle and not supposed to be loaded explicitly. - Let every package keep it's own version number and give the bundle the number of the oldest package, namely
foo. This also seems odd since the packages in the bundle are going to be updated together. Also I'd again have to keep track of three different version numbers.
I looked into the packages of different bundles but couldn't find a “preferred solution”. Most of them seem to give each package the number of the bundle (i.e. approach 2).
Do you have any suggestions? What would you do or consider the best way to proceed? If you had a similar problem: what did you do?
2.:1.would be unusual,3.could lead to confusion, but2.seems to be the simplest and most safe solution for me. – Stephen Jan 27 '12 at 18:38