On Jun 12, 2007, at 12:55 PM, Marius Mauch wrote: Hi Marius,
Not realistic. Think about it: - upstream location for a package changes, so old SRC_URI stops working. If we don't update the existing ebuild people can't use it anymore, if we bump it to a new revision existing users "have to" perform a pointless update.
In that case I agree to keep the version number, but mostly some other stuff is changed too, i.e. dependencies and the version number is still kept the same.
- a mistake in the ebuild prevents installation for 10% of the users, but doesn't affect runtime behavior. SHould we bump it just for that and "force" the other 90% of the users to perform a pointless update?
Yes. This is in general a good idea, any mistake in an ebuild should be corrected by increasing the version number. I am not aware what the guide-lines say, but it is my opinion to let others know: the ebuild was buggy, see changelog... bla bla bla
- also due to eclasses this is practically impossible, if an eclass is changed all ebuilds inheriting it are implicitly changed as well, you can't really restrict that to revbumps.
Well, I am not very familiar with eclasses, may be somebody else can give a hint?
Chers, Cecilia -- [EMAIL PROTECTED] mailing list
