DragonFly kernel List (threaded) for 2003-08
Re: new sysinstall
0$269$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <slrnbkvm7b.oig.weingart@xxxxxxxxxxxxxxxxxxxxxxx> <20030829184829.2fedd129.cpressey@xxxxxxxxxxxxxxx> <200308300659.h7U6xOM0059135@xxxxxxxxxxxxxxxxxxxx> <3f50871c$0$269$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <3f50ab95$0$269$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200308302143.h7ULhrtG065363@xxxxxxxxxxxxxxxxxxxx> <3f512938$0$271$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <Xns93E7C3F58A0ACjustinshiningsilence@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Trace: 1062296384 crater_reader.dragonflybsd.org 271 220.127.116.11
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:769
Justin C. Sherrill wrote:
> Richard Coleman <richardcoleman@xxxxxxxxxxxxxx> wrote in
>>With that said, I think it is more important that SOME scripting
>>language (perl/python/icon/tcl/ruby/whatever) be put in the base
>>system and extensively used, rather than which one is picked. There
>>are many languages that would be suitable. I just happen to think
>>that tcl is a good choice. I just hope that Dragonfly can avoid the
>>mishmash of scripts that are used in FreeBSD.
> 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.
So, hide the "system" version so it is not in the default path.
We shouldn't let such annoyances prevent us from making any progress.
Do we really want to be doing everything with "sh" and "make" forever?
God, I hope not.