On Tue, 27 Dec 2005 19:27:01 +0100 Carsten Lohrke <[EMAIL PROTECTED]> wrote: | - We speak about ebuilds, which are installed and need to be | reinstalled. There is no version cycling (or I do not get what you're | after, please explain in that case).
foo-1.0: DEPEND="=foo-2.0" foo-2.0: DEPEND="" foo-3.0: DEPEND="=foo-1.0" bar-1.0: DEPEND="=foo-1.0" baz-1.0: DEPEND="=foo-2.0 bar" moo-1.0: DEPEND="=foo-3.0 baz" # emerge moo -pv One solution for this particular case, assuming I didn't get confused and screw it up: [n] foo-2.0 [d] foo-1.0 [n] bar-1.0 [u] foo-2.0 [n] baz-1.0 [d] foo-1.0 [u] foo-3.0 [n] moo-1.0 Notice how we have to repeatedly upgrade and downgrade foo. | - Changed use flags will be processed by the normal dependency | calculation of the ebuilds to be rebuilt which may lead to additional | dependencies or blockers. It could also be that some ebuilds are | installed, which do not exist in the repository anymore. Again, you can get cycling. This one's even nastier, if you have various packages that DEPEND upon something built with [foo], various packages that DEPEND upon something built with [!foo] and upgrade / downgrade cycling on that package... | > you may find the PCP somewhat useful...) | | PCP - pretty colored potato? I don't know the abbreviation. Please | explain it and whatelse I miss in your eyes. Post's Correspondence Problem. It's a proven general case unsolvable problem that looks suspiciously similar to the general case "dependency resolution with cycling" situation... -- Ciaran McCreesh : Gentoo Developer (I can kill you with my brain) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
signature.asc
Description: PGP signature
