steve at tightrope.demon.co.uk
Sat Aug 30 17:13:33 PDT 2003
0$269$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <slrnbkvm7b.oig.weingart at xxxxxxxxxxxxxxxxxxxxxxx> <20030829184829.2fedd129.cpressey at xxxxxxxxxxxxxxx> <200308300659.h7U6xOM0059135 at xxxxxxxxxxxxxxxxxxxx> <3f50871c$0$269$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <3f50ab95$0$269$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200308302143.h7ULhrtG065363 at xxxxxxxxxxxxxxxxxxxx> <3f512938$0$271$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <Xns93E7C3F58A0ACjustinshiningsilence at xxxxxxxxxxxxx>
In-Reply-To: <Xns93E7C3F58A0ACjustinshiningsilence at xxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Message-ID: <3f513db3$0$267$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
X-Trace: 1062288819 crater_reader.dragonflybsd.org 267 126.96.36.199
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:767
Justin C. Sherrill wrote:
> Purely from a user perspective, I want to note that having to deal with
> a "system perl" vs. a "user perl" on FreeBSD has been an incredible
> annoyance, especially when trying to work with projects that require
> multiple modules and/or particular versions of Perl. I'd like to not
> have that hassle again.
This isn't a problem just on FreeBSD but Solaris as well with the system
perl and you need to install another Perl namespace since from the Perl
programming perspective the system one is outdated.
I think its a mistake having a "system language" like perl in the path
as /usr/bin/perl and it would be better to "hide" the system language
from third party scripts and modules with a name like
/usr/bin/perl5.005__03 and then have the "user language" installed
through ports (or an updated package system).
Although I suppose the best long term solution is different applications
having different views of some sort of virtual filing system.
More information about the Kernel