From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: language bindings as separate packages
Date: Thu, 01 May 2008 19:05:35 +0300 [thread overview]
Message-ID: <1209657935.13974.10.camel@localhost> (raw)
In-Reply-To: <3c32af40805010852s7fcd150cr9f29acca1f4ecfbd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]
On N, 2008-05-01 at 17:52 +0200, Santiago M. Mola wrote:
> On Thu, May 1, 2008 at 5:09 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> >
> > Hi folks,
> >
> > while building yum, I again ran into trouble because one
> > dependency has to be rebuilt with an specific useflag first
> > (in this case it was libxml2 + python useflag). Actually,
> > there are *lots* of these cases and (AFAIK) portage has no
> > way for properly handling this - it's up to the individual
> > ebuilds to check for those situations and artifically breaking
> > the build. Of coure, breaking builds are ugly.
>
> The proper solution for these cases is implementing USE dependencies,
> which would obsolete pkg_setup checks, and would provide portage with
> info about which USE flags are needed for each dependency. This
> feature is already implemented in other package managers (it's in
> Paludis, maybe in pkgcore too?) and I think we all look forward its
> inclusion in portage.
I do not see that as a solution, but instead maybe only a fix for the
fact that it's failing at some point in an emerge run instead of knowing
beforehand.
It still means a rebuild of the binding providing library, which
involves unnecessary recompilation of the (typically) C or C++ library,
which in some cases can be a huge time sink - that in the case that the
library in question isn't at that time pulled in (in that case the
package manager can enable it at first merge), but already installed
without the bindings USE flags.
So splitting packages is the perfect solution in my opinion, given
unlimited maintainer time and such. In real world that might be too hard
to maintain if upstream doesn't go along, but not in all cases (depends
on how much time the maintainer has, how complex the build system is,
etc).
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-01 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 15:09 [gentoo-dev] RFC: language bindings as separate packages Enrico Weigelt
2008-05-01 15:46 ` Łukasz P. Michalik
2008-05-01 15:52 ` Santiago M. Mola
2008-05-01 16:05 ` Mart Raudsepp [this message]
2008-05-01 16:13 ` Ciaran McCreesh
2008-05-01 16:23 ` Enrico Weigelt
2008-05-01 16:28 ` Ciaran McCreesh
2008-05-01 16:39 ` Enrico Weigelt
2008-05-02 7:26 ` Luca Barbato
2008-05-02 9:00 ` Enrico Weigelt
2008-05-02 9:31 ` Rémi Cardona
2008-05-02 10:21 ` Enrico Weigelt
2008-05-02 15:44 ` Jan Kundrát
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=1209657935.13974.10.camel@localhost \
--to=leio@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