1 |
On Thu, Aug 30, 2012 at 6:39 PM, Michał Górny wrote: |
2 |
> On Wed, 29 Aug 2012 18:18:20 -0400 Mike Frysinger wrote: |
3 |
>> On Wed, Aug 29, 2012 at 6:14 PM, Michał Górny wrote: |
4 |
>> > On Wed, 29 Aug 2012 18:05:19 -0400 Mike Frysinger wrote: |
5 |
>> >> On Wed, Aug 29, 2012 at 6:02 PM, Michał Górny wrote: |
6 |
>> >> > On Wed, 29 Aug 2012 17:50:16 -0400 Mike Frysinger wrote: |
7 |
>> >> >> On Wed, Aug 29, 2012 at 5:42 PM, Michał Górny wrote: |
8 |
>> >> >> > One thing that comes into my mind is finally making pkgconfig |
9 |
>> >> >> > a required, implicit part of toolchain (or @system). Since we |
10 |
>> >> >> > have pkgconf now, this is more feasible than before. |
11 |
>> >> >> |
12 |
>> >> >> i don't think making it part of the toolchain makes sense. i'd |
13 |
>> >> >> rather not add it to @system simply to keep a few packages from |
14 |
>> >> >> sometimes failing. |
15 |
>> >> > |
16 |
>> >> > I'd add it to @system because a lot of packages actually need to |
17 |
>> >> > DEPEND on pkgconfig because they use libraries using .pc files. |
18 |
>> >> > And the number is going to increase, hopefully. |
19 |
>> >> |
20 |
>> >> sure, but keeping things in @system doesn't make much sense: |
21 |
>> >> - there's a penalty (as noted in old threads) |
22 |
>> >> - it isn't actually required at runtime, so it's bloat on reduced |
23 |
>> >> systems |
24 |
>> > |
25 |
>> > I think it's practically the same as compiler. |
26 |
>> |
27 |
>> that isn't a bad view point, but for the purposes of this discussion, |
28 |
>> i don't think it's relevant :) |
29 |
> |
30 |
> Will it be a better view point if I opened a separate discussion about |
31 |
> putting pkg-config in @system? It could get more attention probably. |
32 |
|
33 |
my answer would still be a very strong no |
34 |
-mike |