On Dec 11, 2007 4:47 PM, Ciaran McCreesh <[EMAIL PROTECTED]> wrote: > On Tue, 11 Dec 2007 16:36:51 +0530 > "Nirbheek Chauhan" <[EMAIL PROTECTED]> wrote: > > The idea is that no one would want to automatically upgrade to a > > branch (because you cannot define "upgrade" for branches), so make it > > manual. > > ...and this is why branches shouldn't be treated like versions. They > have their own set of rules and expected behaviours that are best dealt > with by a different proposal.
I made that statement in the context of unversioned branches where you do not know when the branch will be merged. In the case where you do know when the branch will be merged, the versioned branch ebuild can easily be included in the upgrade list via it's version. So, you cannot "upgrade" to app-misc/foo-scm_bblah but you *can* upgrade from app-misc/foo-1.2 to app-misc/foo-1.2-scm_bblahblah and then finally upgrade to app-misc/foo-1.3 when the branch gets merged. -- ~Nirbheek Chauhan -- [EMAIL PROTECTED] mailing list
