On Dec 11, 2007 1:51 PM, Duncan <[EMAIL PROTECTED]> wrote: > But what about when there's a dependency on any of several branches? > That gets hard to maintain if there are multiple ebuilds with similar > dependencies.
How does it become hard to maintain? Different branch ebuilds are still the same package. For example: app-misc/foo-1.2 depends on app-misc/bar branches won't show up in an upgrade, but you can remove app-misc/bar, do an `emerge --oneshot =app-misc/bar-scm_bfeature` and app-misc/foo's dependency will be satisfied. 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. -- ~Nirbheek Chauhan -- [EMAIL PROTECTED] mailing list