public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] virtual/libintl and virtual/iconv
Date: Sat, 7 May 2005 00:32:41 +0200	[thread overview]
Message-ID: <200505070032.42058@enterprise.flameeyes.is-a-geek.org> (raw)

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

That's another discussion birth from G/FreeBSD problems :)

First of all, a bit of introduction on what libintl and iconv are supposed to 
mean:

- libintl is a library which takes care of providing i18n support at runtime 
in applications. This is provided by glibc and probably uclibc on Linux 
systems.
- iconv() is a system function which provides charset conversions to programs. 
This is provided by glibc and uclibc probably, and by other libcs in other 
systems (aix?). *BSD libcs doesn't provide it directly, and some programs 
depends on GNU's implementation. For that, libiconv package was created and 
currently is used by G/FBSD systems.

Now, many ebuilds needs to add to their dependency libiconv and gettext (to 
RDEPEND not just DEPEND) when they aren't used in glibc/uclibc systems.
As this is nasty to add, a solution could be to create two more virtuals, 
provided by glibc and uclibc on Linux systems and by profile on OSX (at least 
for libiconv I think it's already in place), and provided also by gettext and 
libiconv in G/Fbsd (for example).

How good this solution can be?

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)

http://dev.gentoo.org/~flameeyes/


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-05-06 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 22:32 Diego 'Flameeyes' Pettenò [this message]
2005-05-06 22:46 ` [gentoo-dev] virtual/libintl and virtual/iconv Mike Frysinger
2005-05-06 22:56   ` Diego 'Flameeyes' Pettenò
2005-05-06 23:07     ` Mike Frysinger
2005-05-06 23:16       ` Diego 'Flameeyes' Pettenò
2005-05-06 23:31         ` Mike Frysinger
2005-05-06 23:38           ` Diego 'Flameeyes' Pettenò
2005-05-06 23:42           ` Ciaran McCreesh
2005-05-07  1:59             ` Jason Stubbs
2005-05-06 22:49 ` Ciaran McCreesh
2005-05-06 23:00   ` Diego 'Flameeyes' Pettenò

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=200505070032.42058@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@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