From owner-freebsd-ports@FreeBSD.ORG Wed Mar 19 21:59:50 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F6ED106564A for ; Wed, 19 Mar 2008 21:59:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.freebsd.org (Postfix) with SMTP id E9F388FC15 for ; Wed, 19 Mar 2008 21:59:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 23012 invoked by uid 399); 19 Mar 2008 22:04:28 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 19 Mar 2008 22:04:28 -0000 X-Originating-IP: 127.0.0.1 Date: Wed, 19 Mar 2008 14:59:44 -0700 (PDT) From: Doug Barton To: freebsd-ports@freebsd.org Message-ID: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: Utility for safe updating of ports in base system X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2008 21:59:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 A user pointed out to me that on the project ideas page the following entry remains: Write a new utility for the pkg_install suite, possibly named pkg_upgrade(1), implementing a subset of existing portupgrade functionality. The required functionality is: * fixing @pkgdep records in +CONTENTS file * fixing +REQUIRED_BY records * storing old copies of shared libraries after shmajor number change in /usr/local/lib/compat/pkg * upwards and downwards recursive modes http://www.freebsd.org/projects/ideas/index.html#p-ports-upgrade Last year around SoC time I mentioned that if we are going to have such a utility in the base that I would like to have portmaster considered for that role. At the time I was told that I needed to implement the 3rd item on that list, which I did. Portmaster already has the other 3 features, plus a lot more. So, I renew my inquiry. :) Is portmaster a suitable candidate to fulfill the role of the utility described, and if not, why not? Also to rehash a bit of last year's discussion, I don't particularly feel that we _should_ have this type of utility in the base, I think ports stuff should be in the ports tree modulo the few bits needed to bootstrap like pkg_add. However, iff we are going to import _something_, I'd like to have portmaster considered for the job. Thanks, Doug - -- This .signature sanitized for your protection -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEAREDAAYFAkfhjNMACgkQyIakK9Wy8PvXJACfe7UuoxHaQoq20Sb53Xxxg+vg g5QAn0+HQHTcqtbAE51JXlFp943Wmo6A =2y/V -----END PGP SIGNATURE-----