| 1 |
On Thu, 21 Jun 2012 22:35:52 +0200 |
| 2 |
Redcap <maillinglistredcap@×××.de> wrote: |
| 3 |
|
| 4 |
> Hi there, |
| 5 |
> |
| 6 |
> I noticed recently that app-text/acroread has been added |
| 7 |
> as a runtime dependency to Kile. To be honest, I am not |
| 8 |
> familiar with the intricacies fo writing Ebuilds, but I can't |
| 9 |
> see a good reason why Kile should depend on acroread, when |
| 10 |
> okular or some other PDF-viewer is available. Perhaps someone |
| 11 |
> can shed some light on this. |
| 12 |
> |
| 13 |
> Cheers, |
| 14 |
> |
| 15 |
> recap |
| 16 |
> |
| 17 |
|
| 18 |
The dependency in RDEPEND for kile-2.1.2-r1.ebuild reads: |
| 19 |
|
| 20 |
30 RDEPEND="${DEPEND} |
| 21 |
31 $(add_kdebase_dep kdebase-data) |
| 22 |
32 || ( |
| 23 |
33 $(add_kdebase_dep okular 'pdf?,postscript') |
| 24 |
34 app-text/acroread |
| 25 |
35 ) |
| 26 |
|
| 27 |
The || (...) means that Kile depends on either acroread, or okular |
| 28 |
with USE=postscript and also USE=pdf if USE=pdf is set on kile. Check |
| 29 |
your USE flags on Okular if Portage is wanting to bring in acroread |
| 30 |
instead. |
| 31 |
|
| 32 |
Cheers, |
| 33 |
Bryan |
Archives