<div dir="ltr">Zac, Michal,<div><br></div><div>Would you be willing to merge this ?</div><div>If env/ instead of package.env is a deal breaker, I can change that.</div><div>A bashrc like mechanism is more practical for us but package.env will do the trick too</div><div>and we really want to have this in mainline portage.</div><div><br></div><div>Thanks,</div><div>Bertrand</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 18, 2014 at 10:54 AM, Bertrand Simonnet <span dir="ltr"><<a href="mailto:bsimonnet@google.com" target="_blank">bsimonnet@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">For my purpose, I think bash scripting would be more useful. I thought about package.env<div>in the beginning (see first few messages on this thread) as it would help us reuse code but</div><div>variable setting only will limit what we can do.</div><div><br></div><div>If you want package.env, we can implement it too and have both mechanisms available.</div><div><br></div><div>Thanks,</div><div>Bertrand</div><div><div class="h5"><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 18, 2014 at 1:02 AM, Michał Górny <span dir="ltr"><<a href="mailto:mgorny@gentoo.org" target="_blank">mgorny@gentoo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dnia 2014-09-17, o godz. 14:57:10<br> Bertrand Simonnet <<a href="mailto:bsimonnet@google.com" target="_blank">bsimonnet@google.com</a>> napisał(a):<br> <span><br> > I'd rather use the env/ mechanism instead of the package.env one as it is<br> > more flexible.<br> <br> </span>It depends on what you aim to do. As portage(5) points out, both have<br> their advantages:<br> <br> - package.env is parsed early, and so allows you override more<br> variables, like FEATURES,<br> <br> - env/ is used as bashrc extension.<br> <br> The other difference is that package.env supports any atom syntax that<br> the particular EAPI supports, while env/ has hardcoded list of<br> possibilities.<br> <div><div><br> --<br> Best regards,<br> Michał Górny<br> </div></div></blockquote></div><br></div></div></div></div></div> </blockquote></div><br></div>