public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Glibc, non-glibc and external libs
Date: Thu, 16 Jun 2005 16:13:33 +0200	[thread overview]
Message-ID: <1118931213.11254.4.camel@lycan.lan> (raw)
In-Reply-To: <200506161547.39899@enterprise.flameeyes.is-a-geek.org>

[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]

On Thu, 2005-06-16 at 15:47 +0200, Diego 'Flameeyes' Pettenò wrote:
> On Thursday 16 June 2005 00:02, Diego 'Flameeyes' Pettenò wrote:
> > There are other solutions a part the new virtuals?
> Ok just to summarize.
> 
> a) getopt_long isn't important right now, FreeBSD 5 already takes care of it, 
> if in the future it will be necessary for NetBSD, OpenBSD or DragonFly, it 
> will be another issue.
> 
> b) most of the packages requiring gettext at runtime already requires it at 
> build time atm... the simple thing to do is moving this on runtime on the 
> packages which needs when we'll stumble across it
> 
> c) main problem is libiconv, but this is required just by a few packages 
> (gettext, glib2, bogofilter) the other uses it with gettext; as they doesn't 
> require a specific version, we can also add dev-libs/libiconv to glibc's 
> PROVIDE and just depend on dev-libs/libiconv.
> 

The issue I guess is that unlike it seems the common belief in the bsd
camp is, virtuals is not the ultimate cure for all that is twisted.

Rather do something like:

DEPEND="!userland_GNU? ( dev-libs/libiconv )"

(or '!elibc_glibc?' if that is more relevant if it might be needed for
uclibc/whatever)

Just keeping on heaping virtuals for everything is not the only way.  Or
just pull them in the profile.


-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-16 14:20 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     ` [gentoo-dev] " Duncan
2005-06-16  6:18       ` 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 [this message]
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=1118931213.11254.4.camel@lycan.lan \
    --to=azarah@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