On Mon, Aug 9, 2010 at 11:01 AM, Daniel Carrera <dcarr...@gmail.com> wrote: > > I don't think that makes any sense. The Perl package from Debian is > not meant "only for system use". It *is* supposed to be entirely > suitable for you to develop programs in Perl, that's what I use it > for, and this is the first time I ever hear of someone wanting to have > a whole other compile of Perl in order to avoid using the Perl that > came with their Linux distro for no other reason than because it came > with the distro.
It's actually a pretty common practice, and one that I think makes a lot of sense. > Finally, installing the wxPerl package from Ubuntu does not constitute > "mucking about" with the Perl that came with Ubuntu. That makes no > sense. Oh, definitely, I agree there. Any modules installed or updated by the package manager ought be trusted (in theory, anyhow) not to break other system packages. But many *other* things that we do to our local perl installations might *not* play nice with the system perl, which is why we *have* a local perl. It's not unusual to have three or four different perls installed. So it should be possible to install any CPAN module on any installed perl on the system. You can't expect people to use the system perl for their Wx development. -- Eric J. Roode
