| 1 |
On Tue, 2004-12-28 at 15:56 -0600, William Kilian wrote: |
| 2 |
> >/etc/catalyst/catalyst.conf and nowhere else. |
| 3 |
> > |
| 4 |
> > |
| 5 |
> OK. It would be nice for those to eventually move to the spec file so |
| 6 |
> that multiple trees of builds can be easily maintained. |
| 7 |
|
| 8 |
Nope. |
| 9 |
|
| 10 |
Use catalyst -c other-catalyst.conf for separate build trees, if needed. |
| 11 |
|
| 12 |
> The seed is basically devoid of portage configuration data because it |
| 13 |
> shouldn't have an /etc/portage or a /usr/portage/profiles and its |
| 14 |
> make.conf (if any) is ignored. The spec file use flags during an |
| 15 |
> applicable build are functionally equivalent to USE= in make.conf on a |
| 16 |
> normal system. The profile information is provided by the snapshot and |
| 17 |
> portage_confdir provides the information a normal system's /etc/portage |
| 18 |
> directory would provide. The snapshot's profile, target/use, and |
| 19 |
> portage_confdir are used the same way as portage on a normal system uses |
| 20 |
> its profile, USE in make.conf, and portage_confdir. |
| 21 |
|
| 22 |
You got it! |
| 23 |
|
| 24 |
-- |
| 25 |
Chris Gianelloni |
| 26 |
Release Engineering - Operational/QA Manager |
| 27 |
Games - Developer |
| 28 |
Gentoo Linux |
Archives