Hi,
Niko Tyni wrote:
> Cons:
> E increased memory usage on systems running multiple perl processes
> F possibly increased startup time for short perl scripts
> (but that may be a non-issue due to caching anyway?)
This sounds rather concerning to me. The again, I've never noticed any
issues on i386 and kfreebsd-i386.
Since you wrote in #781476 that both, statically and dynamically
linked perl binaries are built anyways and then one is thrown away
depending on the architecture, what about letting the user
respectively administrator choose?
Either by
* shipping both in the perl package and using /etc/alternatives/perl
to choose between the two (perl-dynamic and perl-static) for
/usr/bin/perl, or
* by providing two conflicting packages perl-base and
perl-base-static.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150419122554.gs5...@sym.noone.org
