On Tuesday 27 September 2005 22:44, Diego 'Flameeyes' Pettenò wrote: > On Tuesday 27 September 2005 14:51, Jason Stubbs wrote: > > Variables are _not_ fine. I would think it should be clear to everybody > > by now that ebuilds can not pick random things from the computer they are > > installing on to define how they will build. > > If variables are not fine, so can't be find thigns like profile arch, isn't > it? But that was a solution chosen for the merge of x86 and amd64... > And the same goes with quite everything defined on profile level, like the > others.
ARCH has been specifically protected so that whatever the profile sets it what the ebuilds see, regardless of the user's environment (except for /etc/portage/profile/make.defaults) > I still think that to users it shouldn't give a damn about ELIBC, USERLAND > and KERNEL, as they can just be mislead by thinking that they can change > anything about that.. I'm not suggesting that it should be shown. I'm stating that USE_EXPAND'ed variables in general should be shown to the users. Whether there's a profile control file to hide specific variables is another question. > How we can test for and condition dependencies with special profiles others > than this way? Figure out what you want and then get it supported. Right now, the only variables that you're guaranteed to see in an ebuild function are ARCH and the variables that you find in the ebuild(5) man page. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list
