On Sat, 19 May 2007 07:00:58 +0400, Kent Fredric <[EMAIL PROTECTED]> wrote:

...

Imo, the cyclic dep problem could be solved as thus,

A depends B
    B depends  C||A

Where C is a minimalist subset of A required for building B, which is
only depended on if A is not present.
A is also a replacement for C.

So the flow would go like such.

Emerge A:
  * depends on b
     * A is missing, so depend on C
*emerges C*
*emerges B*
*removes C*  <-- otherwise  A & C containing the same files = headache
*emerges A*

Yes, indeed I agree that we could just do this by hand by changing a
USE flag, but we should at least be open to the idea of looking for a
way to automatically resolve the problem. Computers exist to make our
life easier, not the other way around :)


Just curious: why nobody suggests to allow Portage to use the preferred method of binary distros: emerge several interdependent packages in one transaction. Just prepare the source for A and B and compile both in any order. IMHO this is what the ideal system should do.

--
Andrei Gerasimenko
--
[EMAIL PROTECTED] mailing list

Reply via email to