> Is it accepted practice to allow for changes in an ebuild without changing > the ebuild version number?
It's a bad practice, but it also saves the end user from having to re-emerge packages which have minor changes in them that may or may not affect them. > Background > ---------- > After emerging the latest stable ruby (1.8.2-r1), I found that ruby could > not find some of its modules. The default library paths hardcoded into ruby > were incorrect. To demonstrate: I committed it on Mar 23, and stabilized it on Apr 14th. A minor fix was made by another developer on Apr 19th which should only affect 64 bit users, however, the fix was made with a typo and was caught and fixed on Apr 20th. I guess we took a gamble in not bumping the revision, hoping to not have every Ruby user have to reinstall the package for something that may never have been a problem for them. This decision was helped by the fact that Ruby was rendered useless with this bug, and would force anyone who emerged it during that time would have to seek out some help to sort out the problem. Sorry if it wasn't an obvious solution - a quick look at the ChangeLog and bug reports reference therein quickly provides the resolution. -- [email protected] mailing list
