On Mon, 2004-12-27 at 20:36 -0600, William Kilian wrote:
> Here are some generic questions I have that reference manual doesn't answer:
>
> Where should I specify ${clst_storedir} and ${clst_sharedir}?
> Environment, spec file, envscript?
/etc/catalyst/catalyst.conf and nowhere else.
> Can the grp/use, tinderbox/use, and livecd/use settings include
> negations (-java) and wildcards?
It uses normal portage USE syntax. If portage supports it, then you can
use it.
> For each target, there are possibly use flags, virtuals, keywords, and
> package masks coming possibly from any of: the catalyst spec file; the
> portage_confdir; the snapshot's /usr/portage/profiles; the seed's
The portage_confdir would override whatever is in the portage tree, just
like on a normal system.
> /usr/portage/profiles; the seed's /etc/make.conf; and the seed's
The seed has no /usr/portage/profiles and the make.conf is ignored.
> /etc/portage. For each target, which portage settings come from which
Your seed stage should never have anything in /etc/portage, at all. If
you are using a portage_confdir for one target, then you will need it
for them all (unless it doesn't apply). For example, if you make a
change to glibc in your portage_confdir, then you must use the same
portage_confdir throughout the entire build process, or glibc will be
rebuilt in a later target when emerge --newuse is called. Everything
must be consistent across all targets, otherwise the latest target's
environment takes precedence.
> sources? A table for each target that illustrates what settings comes
> from what location would provide me with a lot more clarity.
It works identical to portage itself.
--
Chris Gianelloni
Release Engineering - Operations/QA Manager
Games - Developer
Gentoo Linux
|
