From owner-freebsd-hackers@FreeBSD.ORG Wed May 14 19:45:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D655E1065678 for ; Wed, 14 May 2008 19:45:34 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.freebsd.org (Postfix) with ESMTP id 699478FC1A for ; Wed, 14 May 2008 19:45:34 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m4EJjUTu008958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 May 2008 05:45:31 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m4EJjU9o064726; Thu, 15 May 2008 05:45:30 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m4EJjTBr064725; Thu, 15 May 2008 05:45:29 +1000 (EST) (envelope-from peter) Date: Thu, 15 May 2008 05:45:29 +1000 From: Peter Jeremy To: Mike Meyer Message-ID: <20080514194529.GB64804@server.vk2pj.dyndns.org> References: <15336578.20080512123806@mail.ru> <200805121153.00809.jonathan+freebsd-hackers@hst.org.za> <1663320218.20080512223531@mail.ru> <20080512152430.3720683e@mbook.local> <2117635718.20080513154406@mail.ru> <20080513121452.GA70860@eos.sc1.parodius.com> <20080513154137.GA28842@pix.net> <482A02CD.7040308@mansionfamily.plus.com> <20080514071728.GP64804@server.vk2pj.dyndns.org> <20080514102410.639f16ef@mbook.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KlAEzMkarCnErv5Q" Content-Disposition: inline In-Reply-To: <20080514102410.639f16ef@mbook.local> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: BDB corrupt X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 19:45:34 -0000 --KlAEzMkarCnErv5Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-May-14 10:24:10 -0400, Mike Meyer wrote: >Just out of curiosity - there seems to be an unspoken assumption that >the ports system can only use tools that are part of the base >system. There have been suggestions that the ports/package infrastructure (pkg_* tools, portsnap etc) be unbundled from the base OS. The difficulty comes when you want to upgrade those components. I know, =66rom experience, that portugrading portupgrade or ruby usually fails as the running portupgrade unexpectedly trips over changed bits of itself. > But this is clearly false - the ports system currently >includes a couple of directories full of software that's not in the >base system. There is a directory full of Makefile includes and another directory full of optional tools but pkg_* sits in the base system. What are you alluding to here. >Adding compiled code to those tools would mean that installing the >ports system gets a bit more complex - you have to run "make install" >after extracting the tarball. Is that so bad it's not going to happen? The problem is not the initial install so much as managing packages and upgrades. I see no problem with having the ports/package infrastructure be part of the ports system as long as: a) A user can install/uninstall/audid (and preferably upgrade) packages without needing to compile anything b) The ports system knows how to upgrade itself without tripping over itself in the process. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --KlAEzMkarCnErv5Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgrQVkACgkQ/opHv/APuIeILACfT2gZ66noHlSlAtFamR+6BW4o vtoAoLzJg88ymeIhmo1yMaQNueiIH/lh =dTjY -----END PGP SIGNATURE----- --KlAEzMkarCnErv5Q--