From owner-freebsd-ports Sat Jul 26 10:46:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA09849 for ports-outgoing; Sat, 26 Jul 1997 10:46:56 -0700 (PDT) Received: from bloke.statsci.com (bloke.statsci.com [206.63.206.184]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA09830 for ; Sat, 26 Jul 1997 10:46:51 -0700 (PDT) Received: (from uucp@localhost) by bloke.statsci.com (8.8.6/8.8.6/UUCP) id KAA13253 for freebsd-ports@freebsd.org; Sat, 26 Jul 1997 10:46:48 -0700 (PDT) >Received: (from scott@localhost) by one.sabami.seaslug.org (8.8.5/8.6.12) id KAA10563 for freebsd-ports@freebsd.org; Sat, 26 Jul 1997 10:39:23 -0700 (PDT) Date: Sat, 26 Jul 1997 10:39:23 -0700 (PDT) From: Scott Blachowicz Message-Id: <199707261739.KAA10563@one.sabami.seaslug.org> To: freebsd-ports@freebsd.org Subject: some port maintenance questions Content-Type: text Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi- I'm working on updating the nmh port and ran across a couple questions. 1) If I do a 'make install' with a different PREFIX than I did the original 'make build', what is the expected behavior? Since the 'configure' step effectively hardcodes a --prefix value into the code, shouldn't the 'install' step try to detect it and error out early? 2) If the port/package has user-customizeable files, how are upgrades supposed to be handled? If you do a 'make install' of the new version while the old is in place, then the pkg db stuff now has 2 packages pointing at the same set of filenames. The new version will (possibly) overwrite the old version of the files...if it tries to save them, then the saved copy won't be in the pkg db at all. Seems the pkg system really needs a pkg_upgrade command (or 'pkg_add -upgrade' option) of some sort? Suggestions? Thanx, Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div) 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org