View previous topic :: View next topic |
Author |
Message |
bobo n00b
Joined: 18 Jul 2002 Posts: 10
|
Posted: Wed Dec 18, 2002 12:16 am Post subject: New ebuilds, same old versions - why? |
|
|
Can anyone out there tell me if there is a policy about updating ebuilds without bumping the version number?
I've just had another occasion when a fix to a broken package (sys-apps/psmisc) didn't get picked up by "emerge rsync", "emerge -u world" because the developer fixed the ebuild but didn't bump the version number.
This is a real pain because wonderful, kind, smart people fix things, but folk don't get the benfit as portage doesn't see a "new" version to update to. |
|
Back to top |
|
|
absinthe Retired Dev
Joined: 06 Oct 2002 Posts: 111 Location: San Francisco, CA, USA
|
Posted: Wed Dec 18, 2002 11:38 am Post subject: Re: New ebuilds, same old versions - why? |
|
|
bobo wrote: | Can anyone out there tell me if there is a policy about updating ebuilds without bumping the version number?
I've just had another occasion when a fix to a broken package (sys-apps/psmisc) didn't get picked up by "emerge rsync", "emerge -u world" because the developer fixed the ebuild but didn't bump the version number. |
Some of these are keyword changes (such as unmasking sparc or ppc) without any real change to the ebuild itself. Believe me, you do not want the version being -r(n) bumped each time someone changes a keyword. This means if you're doing an emerge system/world, you'll likely be recompiling apps that do not need to be recompiled, especially if you're on x86.
Version bumps should happen (imo) only when ebuild bugs have been fixed or new versions of the software is out. Keyword changes, URI corrections, description changes, etc -- all of that isn't worth bumping the ebuild version #. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|