Hi All. This is to inform interested parties that the split (gnat => gnatgcc, gnatgpl, gnatpro) that I was describing recently is now functional and I ma ready to commit the reorganized gnat (p-masked of course at this point). Please see #111340 for details: http://bugs.gentoo.org/show_bug.cgi?id=111340
One issue I wanted to discuss is the naming for the gnat-gpl one. The upstream provides the source under the name of gnat-gpl-2005.tgz. However we have to repackage and mirror it ourselves anyway (this was in fact conclusion from my short discussion with upstream) - 1. upstream has it off dynamic lick that asks to login first (but th package itself is GPL and they give explicit permission for all the repackaging/mirroring as well) 2. The source, as provided, was missing two files, so is deficient in a sense.. So, I have some freedom in making the name sane and src_unpack common to both gnatgcc and gnat-gpl. Problems with the name as it is: gnat-gpl-2005: 1. 2005 stands for the standard revision namme (as in Ada 2005) really rather than for a particular version. While AdaCore (the upstream) promised to change the name when they put out another snapshot I wouldn't hold my breath - with such a name it is easy to forget this even if you have good intentions.. 2. It has a '-' before the number, thus technically making 2005 into a version number, which is a bad choice for a version number. 3. It is inconsistent with gnatgcc naming (it is gnatgcc-3.4.5 atm), while it uses the same backend.. 4. Moving 2005 into a name looks stupid as well - this is just one of the versions really, other packages went through more major changes while keeping the same name and only incrementing major number.. I see two alternatives here: 1. gnat-gpl-2005.1. This keeps it closer to upstream, makes it look like a more real version number and allows trivial increment if an update is released soon (the nearest one is likely to be 2006.1 already although :)) 2. gnat-gpl-3.4.5.1 This uses the backend gcc version as a base, adding a "gnat release indicator" to track gnat-gpl specific changes. Further from upstream naming but simplifies SLOT logic in eclass a lot (in the long run, no need to issue one more conditional for another new version). I am leaning more towards option one (gnat-gpl-2005.1), for "consistency with upstream" reason, as it will be (potentially) less confusing to the users. However I am interested in opinions.. gnatgcc gets renamed to gnat-gcc-3.4.5 for consistency (nothing is committed yet, this is why I am trying to polish the names *now*!). Alternatively gnat-gpl may loose a '-'. I do not have a clear preference on this one, so again, if you care about Ada, plese voice your opinion (either here or in the bug). George -- [email protected] mailing list
