| 1 |
On Tue, 28 Aug 2012 01:03:53 +0200 |
| 2 |
"Andreas K. Huettel" <dilfridge@g.o> wrote: |
| 3 |
|
| 4 |
> Am Dienstag, 28. August 2012, 00:19:28 schrieb Michał Górny: |
| 5 |
> > Right now, it just contains the function Tiziano listed in his |
| 6 |
> > post[1]. I'd appreciate further ideas, feedback, and possibly an |
| 7 |
> > example from someone who will actually need it. |
| 8 |
> |
| 9 |
> How about a function that just outputs the entire required dependency |
| 10 |
> string? Such that we can (similar to add_kdebase_dep) write |
| 11 |
> |
| 12 |
> DEPEND="$(add_boost_dep)" |
| 13 |
|
| 14 |
No, that won't work (soon). Boost is going to be split into smaller |
| 15 |
parts, so I don't want to introduce any dependency generation API which |
| 16 |
will have to change then. |
| 17 |
|
| 18 |
> (Probably we may want to pass parameters here for useflags and |
| 19 |
> version, here's the doc for kdebase_dep from kde4-functions.eclass |
| 20 |
> (and for boost we would not need a package name): |
| 21 |
|
| 22 |
Yes, and that makes it utterly pointless to have a function which just |
| 23 |
converts some random magic string to random magic string + one word :P. |
| 24 |
|
| 25 |
I'd rather give ${BOOST_PKG} to be used in *DEPEND if someone feels |
| 26 |
that being really necessary. But as I said, it's going to be more |
| 27 |
libraries soon. |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny |
Archives