Re: [gentoo-dev] per-package environment variables.

[Anton Starikov <antst@ifm.liu.se>]

Nicholas Jones wrote:
>>1) Possibility to change ENV during building some packages.
> 
> 
> I certainly hope you realize the depths to which people go to
> make your life miserable when attempting to do support.
Yes :) There is something
> The idea is that it takes effort. If it's not trivial, you have to
> LEARN to make it work. Having super-easy things is great, but not
> when it happens to make FIXING it super complicated, developers lose.
Yes, but sollution can be simple...some kind of, probably, limitation 
applied, at first (for example ONLY env variables, nothing more in this 
script, onle A=B syntax). And second, idea to get this environment 
BEFORE something. So, it should be absolutely equal, theoretically, to 
something like this:
CC="bla-bla-bla" CFLAGS="bla-bla-bla" I_WANT_THAT="bla-bla-bla" emerge 
nice_package
I thing that is OK, because anyway users can do it now :)

> Some of this might be nice. If you're going to make this kind of
> effort, why not integrate it into the ebuild?
If I uderstand right, you mean make copy of 10 ebuilds into local 
overlay and edit them twice a week? When new version of ebuild is 
coming? :) And in the middle have troubles, because fresh version will 
be at first automatically updated with standard ENV and at morning I'll 
reallize that my code don't want to be linked against of library XXX, 
which was compiled at night with g77 instead ifc or lf95 or pgf90 or 
something else ? :) That is boring. I've checked already :)


>>4) BTW, in such case it also not bad to have option to include something 
>>like
>>USE="ifc"
>>into this environment, and it should be parsed in proper way. I hope 
>>that this is clear. If we want to build something with IFC and set 
>>proper variables, we really don't want to go and edit one more file 
>>(/etc/portage/package.use). And we don't want to edit also two files, 
>>when we will figure out that we like coming gfortran :)
> 
> 
> Absolutely not. This violates portage's dep calculations and is
> completely wrong. Please do not change any variables that are
> READONLY inside of ebuild.sh after the depend phase.
Again. Idea of this way is to have something equal to
CC="bla-bla-bla" CFLAGS="bla-bla-bla" I_WANT_THAT="bla-bla-bla" 
USE="I_dont_want_that" emerge nice_package
This way is OK and works now. Yes, it probably going to be a bit 
complicated and probably you will need to parse it twice...that is 
subject of dicussion.


> Some of the ideas actually look trackable, which I happen
> to like. Inline definitions of variables, I am not
> particularly fond of.
> 
> If portage has a way to accurately track these files and
> there is a way to avoid arbitary inclusion, then it might
> be a lot more feasable.
Keep in mind, it was a first iteration :) Not really well designed
Just wanted to rise discussion. After which idea could take shape of 
brilliant :)


> Eh. That is all I have to say.
> I'm going to go home and take a nap now.
:)

-- 
Anton Starikov

--
gentoo-dev@gentoo.org mailing list