On Nov 2, 2005, at 3:04 PM, Marc Espie wrote:
The main objection you can have is that this is too complicated,
but so
far, we haven't been able to find any hole in that scheme...
Opinions ?
It's too complicated :). Actually it's not, but it'll confuse the
folks adding packages.
How about something that RPM does (or used to do, it's been a while)
is use an *internal* version number in cases like this. It's
basically the same thing as the v* idea only it's hidden in the
Makefile.
So in the gcc case instead of v0 gcc-3.3.6 would get "VINDEX=0" in
it's Makefile.
This would have the same effect as the v* number but the end user
wouldn't be faced with a potentially freakish gcc-3.3.6v0p3.
My $.02
Marc
