From owner-freebsd-ports Tue Nov 28 14: 8:57 2000 Delivered-To: freebsd-ports@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 1E46937B400 for ; Tue, 28 Nov 2000 14:08:53 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id OAA11747; Tue, 28 Nov 2000 14:08:47 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id eASM8lO60591; Tue, 28 Nov 2000 14:08:47 -0800 (PST) (envelope-from bmah) Message-Id: <200011282208.eASM8lO60591@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Peter Pentchev Cc: "Jason R. Mastaler" , freebsd-ports@FreeBSD.ORG Subject: Re: NetBSD package system features In-Reply-To: <20001128231806.A318@ringworld.oblivion.bg> References: <00112811292900.19785@nightshade> <20001128231806.A318@ringworld.oblivion.bg> Comments: In-reply-to Peter Pentchev message dated "Tue, 28 Nov 2000 23:18:06 +0200." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1899654642P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 28 Nov 2000 14:08:47 -0800 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_1899654642P Content-Type: text/plain; charset=us-ascii If memory serves me right, Peter Pentchev wrote: > On Tue, Nov 28, 2000 at 11:29:29AM -0700, Jason R. Mastaler wrote: > > I've been looking at the NetBSD package system lately to see how it > > compares to FreeBSD's. It seems to have quite a few additional > > features. > > > > For one thing, it has more "make" targets. Has anyone looked into > > incorporating these? Here are some noteworthy examples. For more > > info, see More != better. :-) But in seriousness, I thought there was some talk about adopting some parts of NetBSD's pkgsrc system for FreeBSD, discussed on this list at one point in the past. > Some of these already exist in the Ports collection in one way or another. > > > * update: > > This target causes the current package to be updated to the latest > > version. The package and all depending packages first get > > deinstalled, then current versions of the corresponding packages > > get compiled and installed. This is similar to manually noting > > which packages are currently installed, then performing a series of > > "make deinstall" and and "make install" (or whatever DEPENDS_TARGET > > is set to) for these packages. > > This is being done at the moment - the -o (origin) option to pkg_add, > and some changes to bsd.port.mk, which I believe are already implemented > in -current and are awaiting MFC real-soon-now. Well...almost but not quite. I think the work with pkg_add and bsd.port.mk is a prerequesite to doing an update target. The pkg_add modification is in 5-CURRENT and 4-STABLE; the bsd.port.mk is awaiting a commit. This won't give us the automagic package updating capabilities, but it'll help. > > * show-downlevel: > > This target shows nothing if the package is not installed. If a > > version of this package is installed, but is not the version > > provided in this version of pkgsrc, then a warning message is > > displayed. This target can be used to show which of your installed > > packages are downlevel, and so the old versions can be deleted, and > > the current ones added. > > pkg_version, which will get even better once port origins work. Yep. Actually, if you go and apply the upcoming bsd.port.mk patch (see above), pkg_version will use the origin information in any ports installed after that. I've been running my workstations that way for a couple months. > > * show-pkgsrc-dir: > > This target shows the directory in the pkgsrc hierarchy from which > > the package can be built and installed. This may not be the same > > directory as the one from which the package was installed. This > > target is intended to be used by people who may wish to upgrade > > many packages on a single host, and can be invoked from the > > top-level pkgsrc Makefile by using the target > > "show-host-specific-pkgs" > > Hmm.. That sounds a little like pkg_info with the origin option. > > * bulk-package: > > Used to do bulk builds. If an appropriate binary package already > > exists, no action is taken. If not, this target will compile, > > install and package it (and it's depends, if PKG_DEPENDS is set > > properly, see section 3.2.1). After creating the binary package, > > the sources, the just-installed package and it's required packages > > are removed, preserving free disk space. > > make all install package clean? Agreed. Bruce. --==_Exmh_1899654642P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6JCzv2MoxcVugUsMRAmOQAKCQpRp9X1fuIaust6CVZZw6JzgljQCcCjqT wJAg4/rBWiqeD8+y+BAyOnI= =hm2B -----END PGP SIGNATURE----- --==_Exmh_1899654642P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message