1 |
Often packages depending on X11 libraries will also have to specify |
2 |
the X11 libraries' proto packages in DEPEND. This is because the X11 |
3 |
library itself #includes files provided by the proto package. It's not |
4 |
really that the X11 library depends on this at run-time, so the |
5 |
protocol packages aren't specified in the RDEPEND of the libraries. |
6 |
|
7 |
This is documented in a number of bug reports (see 379545), and it |
8 |
seems that the decision is between |
9 |
- add proto package to dependency list of packages using X11 libs |
10 |
- add proto package to rdepend list of the relevant library itself |
11 |
|
12 |
The first is more correct, I think, but it's also much more annoying. |
13 |
Mesa winds up having x11-proto/inputproto in DEPEND for some long |
14 |
forgotten reason, for instance. |
15 |
|
16 |
The second option is much simpler and less error prone, but removes |
17 |
the ability to depclean the proto packages. |
18 |
|
19 |
It seems that some sort of DEPEND variable that means "I only need |
20 |
this when other packages are building against me" would be useful. |
21 |
Thoughts? |
22 |
|
23 |
Matt |