On Sep 27, 2005, at 8:44 AM, 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.
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..
How we can test for and condition dependencies with special
profiles others
than this way?
[Portage devs please don't throw rocks at me]
My impression of the userland, elibc, and kernel use expanded vars is
it was a quick way to sidestep some of the issues with GLEP22... it
would seem the full keywords have still not been taken advantage of.
From the ebuild perspective, if the profile has a keyword of x86-
fbsd-bsd-fbsd, there is no clean way to just do a conditional based
on a 'Keyword Fragment' as there are obviously namespace collisions.
Ideal to me would be syntax something like:
kernel !fbsd && foo
libc glibc || bar
userland darwin && boof
Probably not feasible, but seems the cleanest in the context of
ebuilds IMHO.
--Kito
--
gentoo-dev@gentoo.org mailing list
