public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@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: Sat, 2 Mar 2013 11:55:12 +0100	[thread overview]
Message-ID: <20130302115512.10c1eedb@portable> (raw)
In-Reply-To: <512E76B9.2050201@gentoo.org>

On Wed, 27 Feb 2013 22:12:25 +0100
Thomas Sachau <tommy@gentoo.org> wrote:

> Pacho Ramos schrieb:
> > 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)
> > 
> 
> multilib-portage has no issues with abi-specific headers, since those
> are installed into a seperate abi-specific location
> inside /usr/include with a wrapper in the original location to not
> break depending packages.

yes, thats the kind of solution that should be implemented for
freetype too. putting all headers under /usr/lib doesnt seem sane.
There exist default locations for headers for a reason, leveraging the
issue to using pkg-config seems wrong.


  reply	other threads:[~2013-03-02 10:55 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
2013-02-27 21:12           ` Thomas Sachau
2013-03-02 10:55             ` Alexis Ballier [this message]
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=20130302115512.10c1eedb@portable \
    --to=aballier@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