[gentoo-dev] Re: Catalyst and logical emerge problem

[Duncan]

Lars Kneschke posted <112d3893029e224082c92d72a3bae92f@192.168.4.1>,
excerpted below,  on Thu, 10 Jun 2004 07:42:11 +0000:

> As you see, sasl can only become compiled after openldap is emerged and
> openldap can only become compiled after sasl is emerged. It's little bit
> tricky. Is there a way to solve this problem?

The usual solution to such "circular dependencies" is to either:

emerge one with the useflag for the other set -<flag>, then emerge the
other with the proper useflags, then emerge the first again with the
desired flags,

or

emerge --nodeps one of them, then emerge the other, then the first again
if there are issues.

Take the following with the caveat that I'm not a Gentoo devel, and may be
giving "improper" advice, from their perspective.  I've seen the above
posted by others, but the following is mine.  However, it should work..
and what is open source for, if not the ability to customize for your own
use?

It's also possible, for catalyst liveCD builds, that one makes use of the
build or bootstrap useflags.  This is how stage one circular dependencies
are normally handled.  These flags limit additional functionality (in the
ebuilds that use them) so they can be built with a minimal system,
normally under conditions such that they will be rebuilt in a later stage
with appropriate operational parameters.

The docs for these flags say do NOT set them for ordinary use.  However,
doing your own LiveCD isn't "ordinary use".  Even if the flags aren't used
by the packages normally, for your own customized LiveCD, you could
customize the ebuilds as well, either statically, for "snapshot"
installations, or using a customized dynamic patch script, for updated
portage tree installations.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin



--
gentoo-dev@g.o mailing list