1 |
On Fri, Sep 16, 2011 at 12:49 AM, Zac Medico <zmedico@g.o> wrote: |
2 |
> On 09/15/2011 09:42 PM, Matt Turner wrote: |
3 |
>> On Fri, Sep 16, 2011 at 12:32 AM, Matt Turner <mattst88@g.o> wrote: |
4 |
>>> Often packages depending on X11 libraries will also have to specify |
5 |
>>> the X11 libraries' proto packages in DEPEND. This is because the X11 |
6 |
>>> library itself #includes files provided by the proto package. It's not |
7 |
>>> really that the X11 library depends on this at run-time, so the |
8 |
>>> protocol packages aren't specified in the RDEPEND of the libraries. |
9 |
>>> |
10 |
>>> This is documented in a number of bug reports (see 379545), and it |
11 |
>>> seems that the decision is between |
12 |
>>> - add proto package to dependency list of packages using X11 libs |
13 |
>>> - add proto package to rdepend list of the relevant library itself |
14 |
>>> |
15 |
>>> The first is more correct, I think, but it's also much more annoying. |
16 |
>>> Mesa winds up having x11-proto/inputproto in DEPEND for some long |
17 |
>>> forgotten reason, for instance. |
18 |
>>> |
19 |
>>> The second option is much simpler and less error prone, but removes |
20 |
>>> the ability to depclean the proto packages. |
21 |
>>> |
22 |
>>> It seems that some sort of DEPEND variable that means "I only need |
23 |
>>> this when other packages are building against me" would be useful. |
24 |
>>> Thoughts? |
25 |
>>> |
26 |
>>> Matt |
27 |
>> |
28 |
>> Another similar situation: |
29 |
>> |
30 |
>> https://bugs.gentoo.org/show_bug.cgi?id=342393 |
31 |
> |
32 |
> Maybe the virtual/mesa-build approach that I suggested can be adapted to |
33 |
> other similar situations: |
34 |
> |
35 |
> https://bugs.gentoo.org/show_bug.cgi?id=342393#c23 |
36 |
|
37 |
That would no doubt help the case of Mesa, but as can be seen by |
38 |
http://tinderbox.dev.gentoo.org/misc/rindex/x11-proto/ , there are |
39 |
lots of other cases as well. |
40 |
|
41 |
Matt |