From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE_EXPAND and libcs
Date: Fri, 29 Apr 2005 23:15:48 +0100 [thread overview]
Message-ID: <20050429231548.1fbc2bb6@snowdrop> (raw)
In-Reply-To: <1114812693.21366.15.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Fri, 29 Apr 2005 23:11:33 +0100 Stephen Bennett <spb@gentoo.org>
wrote:
| 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 reason you don't just do all four (five?) at once?
--
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-29 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 22:11 [gentoo-dev] USE_EXPAND and libcs Stephen Bennett
2005-04-29 22:15 ` Ciaran McCreesh [this message]
2005-04-29 22:28 ` Stephen Bennett
2005-05-01 1:56 ` Stephen Bennett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050429231548.1fbc2bb6@snowdrop \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox