From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] moving bzip2 from local to global USE flag
Date: Tue, 31 May 2005 10:16:06 -0400 [thread overview]
Message-ID: <200505311016.06226.vapier@gentoo.org> (raw)
In-Reply-To: <20050531134146.GA9556@dulcinea.dwc.homedns.org>
On Tuesday 31 May 2005 09:41 am, Daniel Westermann-Clark wrote:
> On 2005-05-31 00:56:31 -0400, Mike Frysinger wrote:
> > anyone have probs with moving bzip2 to global ? we currently
> > utilize it in gnupg, xqf, mkvtoolnix, tar, and we could use it in
> > portage in the future
>
> Some ebuilds use the global bzlib USE flag, is another necessary?
> Maybe it should be renamed?
ah, was not aware of said flag ... yes they should be unified ...
personally i think 'bzip2' is a bit more logical ... what do others think we
should use ? just stick with bzlib since it's what we've had it for a while
now ?
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-31 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 4:56 [gentoo-dev] moving bzip2 from local to global USE flag Mike Frysinger
2005-05-31 13:41 ` Daniel Westermann-Clark
2005-05-31 14:16 ` Mike Frysinger [this message]
2005-05-31 17:38 ` Aron Griffis
2005-06-01 0:54 ` Mike Frysinger
2005-05-31 17:58 ` Maurice van der Pot
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=200505311016.06226.vapier@gentoo.org \
--to=vapier@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