From owner-freebsd-stable Sat Feb 21 15:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04820 for freebsd-stable-outgoing; Sat, 21 Feb 1998 15:16:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04815 for ; Sat, 21 Feb 1998 15:16:07 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-248.HiWAAY.net [208.147.148.248]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id RAA30407 for ; Sat, 21 Feb 1998 17:16:02 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id IAA18521 for ; Sat, 21 Feb 1998 08:56:02 -0600 (CST) Message-Id: <199802211456.IAA18521@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: FreeBSD-Stable@FreeBSD.ORG From: David Kelly Subject: Re: Things I'd like to see in 2.2.6 In-reply-to: Message from Richard Wackerbarth of "Fri, 20 Feb 1998 17:22:30 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Feb 1998 08:56:02 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Richard Wackerbarth writes: > > Here's an interesting policy question. > > If some module requires a few patches to work properly in our > OS/File structure, we typically build a "port" which consists of > a Makefile and a set of patch files. > > Now, it the package author incorporates all of our patches, do we > keep the port which now consists of simply a Makefile which > primarily tells where to get the tarball? > > What of a "new" package which starts out without needing patches? Keep the port. Many of us use /usr/ports as our first stop when searching for something. The ability to "make install" to download, compile, and register an application in the package database is a very valuable function to me. Registering it in the package database makes it easier to remove in the future, possibly for an upgrade. When installing a new FreeBSD system one of the things I check is /var/db/pkg on my running system in order to quickly choose packages to be installed on the new system. Actually I'd like to see every file in FreeBSD registered somehow in a package-like database. This would be a good first step toward live binary upgrades of running systems. Much like I routinely do for SGI systems. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message