| 1 |
On Monday 16 January 2006 14:04, Michael Cummings wrote: |
| 2 |
> Just curious whether there is any value at continuing to offer a libperl |
| 3 |
> ebuild (which creates libperl.so for you) and then having perl |
| 4 |
> statically built against an internally generated libperl.a (substitute |
| 5 |
> your platforms appropriate names porters :) Traditionally we offered |
| 6 |
> both libperl's, and perl itself gets statically built against the static |
| 7 |
> library, but I'm just curious if anyone has a use for this still? |
| 8 |
|
| 9 |
if the lib is meant to be used by other packages, then a static version should |
| 10 |
probably be offered for people who want to build static binaries ... although |
| 11 |
atm, the libperl ebuild doesnt actually produce a libperl.a does it ? and |
| 12 |
the perl ebuild installs libperl.a into a private directory which isnt really |
| 13 |
accessible to packages ... |
| 14 |
-mike |
| 15 |
-- |
| 16 |
gentoo-dev@g.o mailing list |
Archives