1 |
On Mon, 14 Feb 2011 12:37:27 -0300 |
2 |
Alexis Ballier <aballier@g.o> wrote: |
3 |
|
4 |
> Have you thought about doing something like what was done for wxwidgets ? |
5 |
> |
6 |
> - an eselect module for out of portage builds |
7 |
> - an eclass creating symlinks for libpng.pc/.so in $T and setting the correct |
8 |
> -L flag for the linker and PKG_CONFIG_PATH for the .pc ? |
9 |
> |
10 |
> Not sure if this would work that easily but that's certainly better than |
11 |
> updating the version scans in every single package when a new libpng comes |
12 |
> out. |
13 |
|
14 |
I wouldn't recommend the wxwidgets method for something like libpng. The |
15 |
biggest wart is that every wxwidgets-using package has to use the framework |
16 |
or things will go haywire. The only thing that makes it maintainable is the |
17 |
relatively small number of these packages. |
18 |
|
19 |
wxwidgets was also designed for parallel installs from the beginning (that's |
20 |
what they claim anyways, we have to do a fair bit of hacking on it), so it has |
21 |
a well-established interface for choosing versions that every package already |
22 |
uses. We just sort of sit in the middle of that and translate. |
23 |
|
24 |
|
25 |
-- |
26 |
fonts, gcc-porting, it makes no sense how it makes no sense |
27 |
toolchain, wxwidgets but i'll take it free anytime |
28 |
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |