From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Lastriting dev-libs/libffi (replaced by USE libffi in gcc itself)
Date: Tue, 01 Jul 2008 22:05:41 +0300 [thread overview]
Message-ID: <486A8005.6030205@gentoo.org> (raw)
In-Reply-To: <1214038874.25133.4.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
Albert Zeyer kirjoitti:
> On Sat, 2008-06-21 at 09:35 +0200, Tiziano Müller wrote:
>> Donnie Berkholz wrote:
>>
>>> On 14:52 Thu 05 Jun , Samuli Suominen wrote:
>>>> # Samuli Suominen <drac@gentoo.org> (05 Jun 2008)
>>>> # Masked for removal in ~30 days by treecleaners.
>>>> # Replaced by USE libffi in sys-devel/gcc. Bug 163724.
>>>> dev-libs/libffi
>>>> dev-lang/squeak
>>>> x11-libs/gtk-server
>>> The latest version of g-wrap (1.9.11) requires the external libffi
>>> released a month or two ago, because it looks for the pkgconfig file
>>> installed by that and not gcc:
>>>
>>> - libffi is no longer distributed with g-wrap, as it is available
>>> as a stand-alone package now (instead of being burried in the
>>> GCC sources).
>>>
>>> Thoughts?
>> I'd vote for an external libffi as well since python currently has to use
>> it's bundled version of it (statically linking against it).
>> Using libffi provided by gcc (and linking dynamically) is no option yet
>> since portage doesn't protect the user from destroying his system by
>> re-emerging gcc without gcj or libffi USE flags (rev-dep check and
>> USE-based deps would be needed).
>
> Isn't it always preferable to separate packages and break them down into
> peaces (in this case have an external libffi) instead of having big
> packages with lots of stuff (in this case GCC) ?
>
The proper solution is use deps.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2008-07-01 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 11:52 [gentoo-dev] Lastriting dev-libs/libffi (replaced by USE libffi in gcc itself) Samuli Suominen
2008-06-05 18:21 ` Albert Zeyer
2008-06-05 18:54 ` David Leverton
2008-06-05 20:54 ` Albert Zeyer
2008-06-06 7:20 ` Luis Francisco Araujo
2008-06-05 19:38 ` Samuli Suominen
2008-06-05 20:15 ` Luis Francisco Araujo
2008-06-06 5:47 ` Donnie Berkholz
2008-06-06 6:52 ` Fabian Groffen
2008-06-12 16:50 ` Marijn Schouten (hkBst)
2008-06-21 7:35 ` [gentoo-dev] " Tiziano Müller
2008-06-21 9:01 ` Albert Zeyer
2008-07-01 19:05 ` Petteri Räty [this message]
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=486A8005.6030205@gentoo.org \
--to=betelgeuse@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