On Thu, 2007-05-24 at 13:14 +0200, Filip Hanik - Dev Lists wrote: > > I'll try to remember to do it for 5.5.x,
Great, pretty sure it was always done in the past. At least till 5.5.23 which was left at 5.5.20. > Remy will opt out doing it, so > you shouldn't depend on it. Ok that's to bad. :( > To Remy's defense, its kind of pain in the butt having a version number > in SVN that get's tagged anyway, Ok, but that tends to differ from most all other open source app, but to each their own. Usually most FOSS apps releasing tagged sources will have the version reflected in the sources as well. So once the app is built, it's version is reflected within the software. Not just on package sources. To bad this was done in the past but won't be done in the future. FOSS projects should care just as much for source releases as binaries. But that is not always the case :( > so you might be better off just keeping the version yourself, right now > you're only releasing plain vanilla ASF stuff, Well I would not call it plain. But we prefer to not modify sources as much as possible. I am patching and modifying the build system. Since we don't want to download any deps. Much less compile/package stuff already compiled like servet/jsp api jars and etc. > but in the future you could add stuff to the release, or modify it, and > hence want to also modify the version number when you build I doubt we will ever modify the version number when we build. Beyond our -rX for that reflects ebuild revision #. I will just ad some sed or etc to the ebuild to take the source version of the tarball and make sure the prop file matches that. :( -- William L. Thomson Jr. Gentoo/Java
signature.asc
Description: This is a digitally signed message part
