From owner-freebsd-hackers Wed Apr 15 17:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01800 for freebsd-hackers-outgoing; Wed, 15 Apr 1998 17:15:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01767 for ; Wed, 15 Apr 1998 17:15:32 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA01846 for ; Wed, 15 Apr 1998 16:44:30 -0700 (PDT) Received: from pau-amma.whistle.com(207.76.205.64) by whistle.com via smap (V1.3) id sma001838; Wed Apr 15 16:44:12 1998 Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.7/8.8.7) id QAA04942 for freebsd-hackers@FreeBSD.ORG; Wed, 15 Apr 1998 16:44:11 -0700 (PDT) (envelope-from dhw) Date: Wed, 15 Apr 1998 16:44:11 -0700 (PDT) From: David Wolfskill Message-Id: <199804152344.QAA04942@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Package management (was Re: Come on guys, close a PR or two, will ya ?) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy lists some good requirements for a package facility. Would it be (sufficiently) useful to also suggest that the content of a package ought to be able to be re-packaged (reasonably straightforwardly)? The objective would be to be able to take a package, install it somewhere, figure out what sort of site-specific costomizations are appropriate, then re-package it for a given site's use. I did something like this for a client once, using Solaris 2.x's tools, and making a "packaged" version of then-current sendmail (so they could have installation of the sendmail package as one of the final stages in a JumpStart installation). Naturally, I documented how to re-make the package, so when they wanted to migrate to the next release of sendmail, it wouldn't be too painful. (Yes, the information I wrote up is retrievable, in case anyone wants it.) My perspective, here, is as a sysadmin of several machines; I readily understand that folks adaministering a small number of machines would probably find this of less interest. For that matter, things that would install on a network-visible device (as we have /usr/local/*) would also fail to get all that much benefit from this consideration. david -- David Wolfskill dhw@whistle.com (650) 577-7158 pager: (650) 401-0168 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message