On Thu, Sep 10, 2015 at 02:33:09PM +0200, hasufell wrote: > On 09/10/2015 02:25 PM, Rich Freeman wrote: > > > > gtk2+gtk3 in RAM at the same time has a higher memory footprint than > > either one alone. If any package uses one or the other, it will end > > up being loaded into RAM, so there is potentially value in using one > > of them exclusively. > > > > So you are saying for the unlikely case that someone runs gentoo on a > desktop system where he cannot even compile gcc, llvm and others without > waiting for 2 weeks or setting up his on binhost, we have to provide a > backup-path for him, so that gtk3 is not loaded into his RAM?
That was my situation until very recently. Firefox builds took ~6 hours. gcc took 2-3 hours. Even though gtk is not that big, it still took 15ish minutes for me to build. If upstream gives the option of gtk2 or gtk3, why shouldn't the ebuild? >From the "I want a usable system with as little code as possible" and "I want a system tailored to my needs" standpoints, having only one version of gtk makes quite a bit of sense. Alec
