From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/freetype: freetype-2.4.11-r1.ebuild ChangeLog
Date: Wed, 27 Feb 2013 21:25:19 +0100 [thread overview]
Message-ID: <1361996719.1929.10.camel@belkin4> (raw)
In-Reply-To: <20130227192722.65a55ac5@portable>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
El mié, 27-02-2013 a las 19:27 +0100, Alexis Ballier escribió:
[...]
> > The reason I bring this up again is that there was a strong argument
> > yesterday in #gentoo-dev, so it seems the situation is NOT clear.
>
> What are these arguments ? The IRC conspiracy is hard to follow :)
>
I also read that argument... but it looked to turn more in a "personal"
flame war than anything "technical". For example, I couldn't see how
multilib-portage solves the issue of different headers provided for
different arches (that looks to be the key problem that mgorny tried to
solve in freetype)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-27 20:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130225222029.D84D12171D@flycatcher.gentoo.org>
2013-02-27 17:10 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/freetype: freetype-2.4.11-r1.ebuild ChangeLog hasufell
2013-02-27 17:58 ` Alexis Ballier
2013-02-27 18:14 ` hasufell
2013-02-27 18:27 ` Alexis Ballier
2013-02-27 19:05 ` hasufell
2013-02-27 19:09 ` Ciaran McCreesh
2013-03-02 11:08 ` Alexis Ballier
2013-03-02 15:01 ` hasufell
2013-02-27 20:25 ` Pacho Ramos [this message]
2013-02-27 21:12 ` Thomas Sachau
2013-03-02 10:55 ` Alexis Ballier
2013-02-27 20:30 ` Pacho Ramos
2013-02-27 21:08 ` Thomas Sachau
2013-02-27 21:18 ` Michał Górny
2013-03-02 10:53 ` Alexis Ballier
2013-02-27 18:15 ` Diego Elio Pettenò
2013-02-27 20:20 ` Pacho Ramos
2013-02-27 20:23 ` Ciaran McCreesh
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=1361996719.1929.10.camel@belkin4 \
--to=pacho@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