Dnia 2014-09-17, o godz. 14:57:10 Bertrand Simonnet <bsimon...@google.com> napisał(a):
> I'd rather use the env/ mechanism instead of the package.env one as it is > more flexible. It depends on what you aim to do. As portage(5) points out, both have their advantages: - package.env is parsed early, and so allows you override more variables, like FEATURES, - env/ is used as bashrc extension. The other difference is that package.env supports any atom syntax that the particular EAPI supports, while env/ has hardcoded list of possibilities. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
