| 1 |
* Enrico Weigelt <weigelt@×××××.de> schrieb: |
| 2 |
|
| 3 |
> > pretty please force every consumer to hardcode the version |
| 4 |
> > because i know people that want to do this" ? |
| 5 |
> |
| 6 |
> No, they should use pkg-config at buildtime and do the version |
| 7 |
> selection there (eg. the eselect-way). |
| 8 |
|
| 9 |
Oh, it gets a bit tricker: the dependencies of the installed |
| 10 |
packages will have to be fixed to the actually used version/slot. |
| 11 |
|
| 12 |
hmm, maybe this also could be done via some eclass, that adds |
| 13 |
an useflag for libpng version selection ? |
| 14 |
|
| 15 |
I could imagine a way like that: |
| 16 |
|
| 17 |
* libpng15 is installed in a way that it doesnt conflict with existing |
| 18 |
libpng14 (different locations, pkg-config name, slotted, etc) |
| 19 |
* pass pkg-config calls through a wrapper that automatically |
| 20 |
chooses the right .pc file on some environment variable etc. |
| 21 |
* each libpng-using package that should be buildable against libpng15 |
| 22 |
is changed to use the new eclass (that does all the switching magic) |
| 23 |
|
| 24 |
IMHO this should allow keeping the (runtime) dependencies intact |
| 25 |
(no revdep-rebuild required) and allow an smooth upgrade. When |
| 26 |
everything had been rebuilt against libpng15 one day, --depclean |
| 27 |
would kick off old libpng14. |
| 28 |
|
| 29 |
|
| 30 |
cu |
| 31 |
-- |
| 32 |
---------------------------------------------------------------------- |
| 33 |
Enrico Weigelt, metux IT service -- http://www.metux.de/ |
| 34 |
|
| 35 |
phone: +49 36207 519931 email: weigelt@×××××.de |
| 36 |
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 |
| 37 |
---------------------------------------------------------------------- |
| 38 |
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme |
| 39 |
---------------------------------------------------------------------- |
Archives