Amit Dor-Shifer wrote:
Thanks.
IMHO this usage of env.d should be documented in the ebuild howto, as it
presents a useful-yet-not-trivial mechanism.
I'd document it, if:
a) I get no objection from others. Anyone?
b) I'd be referred to the proper place to document it in. There's a page
Does emerge actually call 'env-update'? If so, where (I can't find in in
the code)?
if not, who performs the environment update when an ebuild is emerged
(I'm supposing env-update gets called. I didn't call it explicitly in my
ebuild, yet still /etc/profile.env gets updated with
Amit Dor-Shifer wrote:
Does emerge actually call 'env-update'? If so, where (I can't find in in
the code)?
if not, who performs the environment update when an ebuild is emerged
(I'm supposing env-update gets called. I didn't call it explicitly in my
ebuild, yet still /etc/profile.env gets
