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