public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493)
Date: Thu, 13 Feb 2014 00:56:54 +0100	[thread overview]
Message-ID: <1392249414.22926.5.camel@kanae> (raw)
In-Reply-To: <52FBF9D6.7010104@gentoo.org>

Le mercredi 12 février 2014 à 17:46 -0500, Chris Reffett a écrit :
> splits it into two
> separate packages, and I suspect that the times where you will have to
> rebuild are when a package needs webkit-gtk to support another toolkit
> (which should happen only once), and when you upgrade (in which case
> you would be updating them separately anyway). I also fail to see what
> this has to do with binpkgs: if something needs webkit-gtk[gtk2], you
> add a dep on webkit-gtk[gtk2]. The user adds USE=gtk2 to webkit-gtk if
> needed, webkit-gtk binpkg gets rebuilt. I see no breakage there

Actually changing a USE flag on a package such as webkit-gtk has a huge
cost.

If say you build with USE=gtk3 then suddenly need gtk2, you not only
build what you need, you will also have to rebuild gtk3 support which
you already have though. Since this takes a decent amount of time, even
on a one year old i7, I don't know about you, but I am pretty sure users
will start to complain about this as well.

You would have to build, webkit1 for gtk2, webkit1 for gtk3 and webkit2
for gtk3.

The story is the same for almost all libs that support both toolkits,
you end up rebuilding everything even if you already have one.
webkit-gtk is just the best example to prove you this is a bad idea.

-- 
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo



  reply	other threads:[~2014-02-12 23:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 22:39 [gentoo-dev] RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493) Alex Alexander
2014-02-11 23:04 ` Samuli Suominen
2014-02-11 23:51   ` Ulrich Mueller
2014-02-12  0:00     ` Samuli Suominen
2014-02-12  0:20       ` Ulrich Mueller
2014-02-18  9:39   ` Ben de Groot
2014-02-19 17:40     ` Sergey Popov
2014-02-11 23:13 ` Gilles Dartiguelongue
2014-02-12  0:33   ` Chris Reffett
2014-02-12  6:27     ` [gentoo-dev] " Ryan Hill
2014-02-12  7:23     ` [gentoo-dev] " Pacho Ramos
2014-02-12  8:09     ` Michał Górny
2014-02-12 22:46       ` Chris Reffett
2014-02-12 23:56         ` Gilles Dartiguelongue [this message]
2014-02-13  0:22         ` Matt Turner
2014-02-12  8:10     ` Gilles Dartiguelongue
2014-02-13  0:45       ` [gentoo-dev] " Ryan Hill
2014-02-21  3:19   ` [gentoo-dev] " Donnie Berkholz
2014-02-12  7:29 ` Lars Wendler
2014-02-12  8:14   ` Gilles Dartiguelongue
2014-02-12  8:05 ` Michał Górny
2014-02-12  9:14   ` Tom Wijsman

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=1392249414.22926.5.camel@kanae \
    --to=eva@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