| 1 |
On Saturday 27 December 2003 16:51, Caleb Tennis wrote: |
| 2 |
> In trying to track down some of the dependency problems/mess in the KDE |
| 3 |
> stuff, I come to you with a question: |
| 4 |
> Sorry if this is stupidly obvious, but it's not addressed in the docs and |
| 5 |
> nobody has been able to answer the question thus far. |
| 6 |
|
| 7 |
it's not stupid nor is it really a 'someone screwed up big' ... |
| 8 |
|
| 9 |
newXdepend has some history behind it but it seems you only care about the |
| 10 |
now ... i think danamark will have some issues when he gets back but i hope |
| 11 |
that it turns out well ... |
| 12 |
|
| 13 |
the way dependencies work right now with respect to eclasses is pretty |
| 14 |
simple ... |
| 15 |
|
| 16 |
eclasses ALWAYS use newdepend, newrdepend, newpdepend, newcdepend ... they |
| 17 |
should NEVER have DEPEND= or similar ... |
| 18 |
flip side of the coin is that ebuilds should not be using the newXdepend, they |
| 19 |
should be using DEPEND= ... |
| 20 |
|
| 21 |
i think thats clear enough so i'll leave this alone ;) |
| 22 |
-mike |
Archives