public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergey Popov <pinkbyte@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Better handling of USE flags to enable/disable system libraries
Date: Wed, 29 May 2013 10:28:48 +0400	[thread overview]
Message-ID: <51A5A020.1070009@gentoo.org> (raw)
In-Reply-To: <1430868.1g3PJOlj7u@darkness>

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

29.05.2013 03:01, David Carlos Manuelda пишет:
> El Martes, 28 de mayo de 2013 14:03:52 Mike Frysinger escribió:
>> On Tuesday 28 May 2013 13:53:54 Michał Górny wrote:
>>> On Tue, 28 May 2013 16:43:10 +0200 David Carlos Manuelda wrote:
>>>> I posted a bug about that along with a suggestion, despite sometimes I
>>>> do
>>>> not explain myself correctly (I am very sorry): bug #471590
>>>>
>>>> Many packages are bundling its own libraries rather than link against
>>>> system ones, and there is a bug tracker for that (bug #251464)
>>>> [...]
>>>> What I propose for example, is a very good and simple approach: to have
>>>> an option in portage's make.conf, something like that (the name may
>>>> change):
>>>>
>>>> 1.- USE_SYSTEM_LIBRARIES="cairo sqlite XXX"
>>>> 2.- USE_SYSTEM_LIBRARIES="* -cairo"
>>>> 3.- USE_SYSTEM_LIBRARIES="*"
>>>
>>> I don't think we should do it like this.
>>>
>>> Bundling libraries is a pathological case. In general, we should work
>>> on fixing this and getting rid of bundled libraries. In that general
>>> case, the flags are not required.
>>
>> +1
>> -mike
> Ok, thinking it better I agree, that having them use system libraries is far 
> better, but why then those affected ebuilds have corresponding USE disabled by 
> default?
> 
How do you imaging use of system library( called "foo", for example) if
foo, bundled in program(called "bar", for same reason :-)) is fork with
new features that is suitable only for "bar"?

It's ideal situation when "bar" works also with system "foo"(not all
features works, however). Sometimes(and it happens very often, to be
honest) "bar" can not work with system "foo" at all! For example, look
at quake3-1.36-r1.ebuild, at commented "use system jpeg" patch. If you
uncomment it, quake3 will be built against system jpeg. It will build
successfully, but textures will be a big mess of polygons.

So, unfortunately, it's not even an option here, unless somebody will do
a great work for splitting this library and write a huge patch, that
will be totally rejected by upstream(so he will have to maintain this
patch on his own).

-- 
Best regards, Sergey Popov
Gentoo developer
Gentoo Desktop Effects project lead
Gentoo Qt project lead


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

      parent reply	other threads:[~2013-05-29  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 14:43 [gentoo-dev] Better handling of USE flags to enable/disable system libraries David Carlos Manuelda
2013-05-28 17:53 ` Michał Górny
2013-05-28 18:03   ` Mike Frysinger
2013-05-28 23:01     ` David Carlos Manuelda
2013-05-28 23:55       ` Rich Freeman
2013-05-29  6:28       ` Sergey Popov [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=51A5A020.1070009@gentoo.org \
    --to=pinkbyte@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