From owner-freebsd-ports Fri Aug 30 07:20:09 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA22473 for ports-outgoing; Fri, 30 Aug 1996 07:20:09 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA22465; Fri, 30 Aug 1996 07:20:05 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id JAA11659; Fri, 30 Aug 1996 09:20:01 -0500 (EST) Date: Fri, 30 Aug 1996 09:20:01 -0500 (EST) From: John Fieber To: Chuck Robey cc: Satoshi Asami , jkh@time.cdrom.com, freebsd-ports@FreeBSD.ORG Subject: Re: Should this port go in ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 29 Aug 1996, Chuck Robey wrote: > I thought about adding some cpp structure to a PLIST, specifically the > ability to do defines and ifdefs. This would allow the PLIST to change > dynamically, depending on variables that existed at the time of package > creation. On unpacking, though, the variables could be different than > when the package was created. Just the other day, as I was dealing with a PLIST that didn't match what actually got installed, I was thinking that there is something fundamentally wrong with the system. The idea I had was to modify install to (optionally) log installations. The logging could be controlled either through command line options or environment variables. Obvious things to log would be the file and a tag (port name), but things like the user, time and file checksum could be added. The latter might be useful when upgrading a port to find files which might have local modifications needing to be preserved. This could even be used for the FreeBSD distribution itself, making upgrades safer and easier. Then, instead of carefully making sure the PLIST matches what is really installed, you just make sure that the port uses install instead of cp to place its files. bsd.ports.mk would set the appropriate environment variables to log the installation. The record of the installation is 100% correct, even if there are variant installation options. The manually maintained PLIST seems to be like flypaper in a barn. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================