| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marius Mauch wrote: |
| 5 |
> And last but not least a CLI option is bound to emerge, but this feature can also be useful for other tools. Checking an env var in the config class would enable it implicitly for all users of portage.py, without it everyone would have to basically duplicate the relevant code from emerge. |
| 6 |
|
| 7 |
I suppose we can make the env variable an optional fallback if the |
| 8 |
config_root parameter is unspecified in the config constructor call, |
| 9 |
but we can't make the env variable mandatory. In order to properly |
| 10 |
support $ROOT, we need to have at least 2 independent config |
| 11 |
instances with separate values of PORTAGE_CONFIGROOT. That way, |
| 12 |
when building packages targeted at $ROOT, build time dependencies |
| 13 |
that need to be merged to / get an independent config (which may be |
| 14 |
completely different from that used for $ROOT). |
| 15 |
|
| 16 |
Zac |
| 17 |
|
| 18 |
|
| 19 |
-----BEGIN PGP SIGNATURE----- |
| 20 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 21 |
|
| 22 |
iD8DBQFFXcse/ejvha5XGaMRAsxcAKDgSQf+sqpQtSI+G+CjGjj92j0p2wCfUY/s |
| 23 |
p6y+l8nhMLHcWXtji502QPA= |
| 24 |
=eWND |
| 25 |
-----END PGP SIGNATURE----- |
| 26 |
-- |
| 27 |
gentoo-portage-dev@g.o mailing list |
Archives