Gentoo Archives: gentoo-dev

From: Alexis Ballier <aballier@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: prune_libtool_files() and pkg-config dependency
Date: Fri, 31 Aug 2012 14:58:49
Message-Id: 20120831105623.4a31e588@gentoo.org
In Reply to: Re: [gentoo-dev] Re: prune_libtool_files() and pkg-config dependency by "Michał Górny"
1 On Fri, 31 Aug 2012 12:42:10 +0200
2 Michał Górny <mgorny@g.o> wrote:
3
4 > On Fri, 31 Aug 2012 10:06:06 +0000 (UTC)
5 > Duncan <1i5t5.duncan@×××.net> wrote:
6 >
7 > > Michał Górny posted on Fri, 31 Aug 2012 10:01:09 +0200 as excerpted:
8 > >
9 > > > On Fri, 31 Aug 2012 00:12:53 +0000 (UTC)
10 > > > Duncan <1i5t5.duncan@×××.net> wrote:
11 > > >
12 > > >> Various people have in fact expressed a desire to REDUCE the
13 > > >> number of packages in @system, for various reasons including both
14 > > >> the parallel merge penalty and the bloat on reduced systems. In
15 > > >> practice, there's not a lot of positive movement on actually
16 > > >> reducing @system, but at minimum, unless there's *NO* other
17 > > >> choice and in this case there clearly is, we shouldn't be ADDING
18 > > >> packages to @system.
19 > > >>
20 > > >> For that reason, while I do see the reason why some would like
21 > > >> pkg-config added to @system, the whole idea's pretty much a
22 > > >> non-starter
23 > >
24 > > > But you're aware that cost of pkgconf is very little?
25 > >
26 > > Not really, when it's a step in the opposite direction from an
27 > > intended goal. The first step toward any goal is to stop going
28 > > backward, and that's exactly what this would be. We need a smaller
29 > > @system, not a larger one, and while the add would be easy, undoing
30 > > it years later when it's yet another bit of the tangled web woven,
31 > > would be *MUCH* more difficult. Just don't do it; don't go
32 > > backward; don't add to the problem instead of reducing it.
33 >
34 > So please introduce virtual/compiler, virtual/linker,
35 > virtual/posix-system, virtual/sratatata and add them to DEPEND of
36 > every single ebuild.
37 >
38 > I believe that the more important direction here is to make
39 > development *easier*, not harder. Adding the same DEPENDs over and
40 > over again to every single package is at least frustrating. Similarly
41 > frustrating would be if those 'reduced systems' had to rebuild gcc
42 > every time they wanted to compile something... oh wait, they would
43 > have to bootstrap it every time.
44 >
45
46 you would achieve it better by adding pkgconfig to DEPEND in
47 eutils.eclass than putting it in @system since in the latter case it
48 would also be a RDEPEND of everything basically
49
50 this doesnt really compare to gcc since its a RDEPEND for everything c++
51 and maybe more (i didnt check when libgcc_s is linked in or not)
52
53 A.

Replies