-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marius Mauch wrote: > 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.
I suppose we can make the env variable an optional fallback if the config_root parameter is unspecified in the config constructor call, but we can't make the env variable mandatory. In order to properly support $ROOT, we need to have at least 2 independent config instances with separate values of PORTAGE_CONFIGROOT. That way, when building packages targeted at $ROOT, build time dependencies that need to be merged to / get an independent config (which may be completely different from that used for $ROOT). Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFXcse/ejvha5XGaMRAsxcAKDgSQf+sqpQtSI+G+CjGjj92j0p2wCfUY/s p6y+l8nhMLHcWXtji502QPA= =eWND -----END PGP SIGNATURE----- -- gentoo-portage-dev@gentoo.org mailing list
