From: Kito <kito@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [G/FBSD] /usr/lib/charset.alias
Date: Fri, 15 Jul 2005 20:15:55 -0500 [thread overview]
Message-ID: <A0BC5362-C0D8-4216-A9F3-7C6B9DD34CD3@gentoo.org> (raw)
In-Reply-To: <200507152045.39771.vapier@gentoo.org>
On Jul 15, 2005, at 7:45 PM, Mike Frysinger wrote:
> On Friday 15 July 2005 08:33 pm, Diego 'Flameeyes' Pettenò wrote:
>
>> On Gentoo/FreeBSD and probably every other system using dev-util/
>> libiconv
>> instead of the glibc-provided one creates the /usr/lib/
>> charset.alias file.
>> Unfortunately this gets conflict over different packages.
Exact same situation with Darwin/OS X...
>>
>
> i thought the packages that create that file do so because they
> were utilizing
> some bundled crap ...
>
> regardless, i think this should be done on a global scale rather than
> per-package ... why not add some bashrc-foo to your profile ?
Globally would definitely be better IMO. But how would bash-fu in a
profile prevent a collision during a merge?
>
> can i get access to a fbsd box so i can test some of this crap ?
> i'd like to
> investigate sed/e2fsprogs and why it installs those files ...
> -mike
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-16 1:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 0:33 [gentoo-dev] [G/FBSD] /usr/lib/charset.alias Diego 'Flameeyes' Pettenò
2005-07-16 0:45 ` Mike Frysinger
2005-07-16 1:15 ` Kito [this message]
2005-07-16 1:20 ` Mike Frysinger
2005-07-16 9:05 ` Diego 'Flameeyes' Pettenò
2005-07-16 17:07 ` Marius Mauch
2005-07-16 17:23 ` Diego 'Flameeyes' Pettenò
2005-07-17 0:26 ` Mike Frysinger
2005-07-17 13:34 ` Diego 'Flameeyes' Pettenò
2005-07-17 14:17 ` Mike Frysinger
2005-07-17 16:03 ` Ned Ludd
2005-07-18 4:47 ` Mike Frysinger
2005-07-19 11:39 ` Ned Ludd
2005-07-19 12:53 ` Mike Frysinger
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=A0BC5362-C0D8-4216-A9F3-7C6B9DD34CD3@gentoo.org \
--to=kito@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