On Tuesday 27 September 2005 12:12, Jason Stubbs wrote:
> Which leads me to the one thing I didn't say but feel strongest about..
> What is the real point of USE_EXPAND? What can/does it do that USE flags do
> not?
They are forced by the profile, as we don't want users to go away WITHOUT them 
when they are needed. That's the main part of it.
Then there's the fact that I can test for a generic BSD libc using [[ ${ELIBC} 
== *BSD ]], too.

> This doesn't quite apply to cross compiling and such, but in general yeah.
Cross-compiling with different libc can be possible (glibc->uclibc) but I'm 
not sure on what extent. Currently trying to have cross-compiling between 
different kernels is a no-go.

The proposal of domains or whatever they are called that Brian talked about 
some time ago when he proposed BDEPEND would probably fix this issue, tho.

> Similar to "build" and "bootstrap"? Note, these aren't hidden either but if
> the ELIBC and friends should be hidden those should be hidden too.
But they have sort of meaning to users, for example with newuse, and does not 
screw your system around, or at least not completely (one can build a few 
packages with build useflag active and still have a working system, at the 
end).
Changing the ELIBC/KERNEL/USERLAND is like using a sparc profile on an x86 ...

Also, most ebuilds does not use the above variables in a complete way, they 
usually check for a certain content (GNU userland, FBSD libc, Linux Kernel).
Saying for example that kdelibs uses kernel_linux can make people think that 
kdelibs works ONLY for Linux kernel, while that's not true at all.
They are special features or workarounds that does not concern users at all.

> And we're back to USE flags again... ;)
As they are the only way to change the dependencies, yeah, always USE is what 
we need. For the most of the uses, variables are fine, but for dependency we 
use them use-expanded.

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)

Attachment: pgpPCWjgDmswh.pgp
Description: PGP signature

Reply via email to