public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Glibc, non-glibc and external libs
Date: Wed, 15 Jun 2005 22:58:06 -0700	[thread overview]
Message-ID: <pan.2005.06.16.05.58.05.899750@cox.net> (raw)
In-Reply-To: 200506160441.44787@enterprise.flameeyes.is-a-geek.org

Diego 'Flameeyes' Pettenò posted
<200506160441.44787@enterprise.flameeyes.is-a-geek.org>, excerpted below,
on Thu, 16 Jun 2005 04:41:34 +0200:

> On Thursday 16 June 2005 01:13, Olivier Crete wrote:
>> Why dont you just add them to the profile as system packages ?
> I though of that but I'm not sure about it. I wish to have a systme
> profile as cleaner as possible and libiconv, gettext and other packages
> aren't needed for a lot of different packages because they doesn't use
> them.

What about dual-tracking?  You say a virtual works but getting it setup is
slow.  You say the profile option works but you don't want to use it due
to bloat.  So... what about kicking off the virtual process now, but put
it in the profile temporarily as well, avoiding having to wait for the
virtual process, with a comment on the profile entry reminding you to
review it with an eye for removal if the virtual process is done, say for
2006.0.

After all, if it's not really required for what folks are doing and they
don't want the bloat, they can package.provided it, as I've done with a
couple things (I HAD to with sash, as I never COULD get the thing to
compile here on amd64, for whatever reason, maybe it requires Linux
Threads and I run nptl-only??? who knows?), so profile system entries
don't make things ABSOLUTELY mandatory.

Seems the reasonable thing to do, here, but then again, I'm likely missing
something.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-06-16  6:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 22:02 [gentoo-dev] Glibc, non-glibc and external libs Diego 'Flameeyes' Pettenò
2005-06-15 23:13 ` Olivier Crete
2005-06-16  2:41   ` Diego 'Flameeyes' Pettenò
2005-06-16  5:58     ` Duncan [this message]
2005-06-16  6:18       ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2005-06-16  9:26         ` Marius Mauch
2005-06-16  9:41           ` Thomas de Grenier de Latour
2005-06-16 11:14             ` Marius Mauch
2005-06-16 13:57     ` [gentoo-dev] " Chris Gianelloni
2005-06-16  4:22 ` Mike Frysinger
2005-06-16  4:33   ` Diego 'Flameeyes' Pettenò
2005-06-16 13:14     ` Mike Frysinger
2005-06-16 13:47 ` Diego 'Flameeyes' Pettenò
2005-06-16 14:13   ` Martin Schlemmer
2005-06-16 15:51     ` Diego 'Flameeyes' Pettenò
2005-06-16 16:07       ` Mike Frysinger
2005-06-16 16:28         ` Diego 'Flameeyes' Pettenò
2005-06-16 14:18   ` Marius Mauch

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=pan.2005.06.16.05.58.05.899750@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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