Date: Fri, 28 Sep 2001 12:42:01 -0500 From: Mike Meyer <mwm@mired.org> To: swear@blarg.net (Gary W. Swearingen) Cc: questions@freebsd.org Subject: Re: Which Ports are what Message-ID: <15284.46697.666469.442953@guru.mired.org> In-Reply-To: <101611947@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary W. Swearingen <swear@blarg.net> types: > Mike Meyer <mwm@mired.org> writes: > > The perl section of the ports is programs/modules *written in* > > perl. > That strikes me as an odd way to categorize software. Actually, it's a very useful category. If I were still a perl developer, having all the ported Perl modules in one place is a good thing. Likewise, if I want to do X in a perl program, having one place to look for ports that almost do X is a good thing, as I can then cut-n-paste then edit that code it to get what I need. Just to be inflammatory, one of the reasons I no stopped writing Perl is that in Python, you're far more likely to be able to import-n-inherit then override methods in that code to get what you need. > I suppose some people don't want Perl on their system and having > the Perl programs integrated with the mainstream (ie, compiled?) > programs causes some kind of problem for them. Isn't there some > way to solve those problems while allowing the Perl programs to be > integrated so people can see them in the regular categories? As Dan mentioned, ports can be in multiple categories, so it's already been done. <mie -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15284.46697.666469.442953>