Date: Sat, 9 May 1998 21:21:41 -0500 (CDT) From: Daniel Ortmann <ortmann@sparc.isl.net> To: wollman@khavrinen.lcs.mit.edu Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/6539: bmake version of perl5 available Message-ID: <199805100221.VAA12261@pyrl.eye> In-Reply-To: <199805092010.NAA18331@freefall.freebsd.org> from Garrett Wollman at "May 9, 98 01:10:05 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> The following reply was made to PR bin/6539; it has been noted by GNATS. > > From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> > To: sjr@home.net > Cc: FreeBSD-gnats-submit@FreeBSD.ORG > Subject: bin/6539: bmake version of perl5 available > Date: Sat, 9 May 1998 16:03:34 -0400 (EDT) > > <<On Wed, 6 May 1998 21:22:38 -0400 (EDT), sjr@home.net said: > > > ftp.freebsd.org:/pub/FreeBSD/incoming/bmake-perl5-1.1.tar.gz > > > This tar file contains: > > > BSD.usr.dist.patch - a patch that adds the perl directories, and > > contrib/perl5 - contains the perl5 code, and > > usr.bin/perl5 - contains the makefiles. > > What *I'd* really like to see would be a <bsd.perl5.mk> system > template, and a modified version of MakeMaker which referenced it. > Then not only would this not be such a nightmare each time a new > version of Perl comes out, but it would also make it much more > convenient to create Perl5 bindings of important system functionality > (e.g., a FreeBSD:: set of modules which interface to our libraries). Precisely. With a collection of perl-AI modules watching/commenting on the configuration the system, and possibly making certain fixes where security is not endangered. [imagine an "emacs" level of live system integration] Some modules (call it a subsystem) could watch system security, a la "satan". Another could analyse diffs to sync /etc/* files with /usr/src/etc/* files. ... building commands that make it easy to upgrade files. It is likely that 50% or more of us already have perl code doing this very thing anyway ... let's just capitalize on existing work. Another could monitor/configure www stuff. Another subsystem could, for example, watch/comment/build ports when currently installed packages have aged. Other modules could watch network sites for newer versions of software and begin the retrieval/inspection/porting process based on the ports patch directory or other prior art. I haven't looked at the cfengine ... is there commonality here? -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805100221.VAA12261>