Hi all,

Since USE_EXPAND has moved into the profiles, and we find ourselves
needing to switch code and dependencies based on the libc in use (mainly
due to glibc being weird and bundling several other libraries together),
I'd like to add a LIBC variable to the profiles, and add it into
USE_EXPAND. That way, ebuilds that need to can handle code specific to
one libc in a vaguely sane manner.

Any objections? Comments?

-- 
[email protected] mailing list

Reply via email to