From owner-freebsd-ports@FreeBSD.ORG Sat May 20 06:34:59 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08EA116A41F for ; Sat, 20 May 2006 06:34:59 +0000 (UTC) (envelope-from plosher-keyword-freebsd.a36e57@plosh.net) Received: from luftpost.plosh.net (luftpost.plosh.net [204.152.186.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id B781343D46 for ; Sat, 20 May 2006 06:34:58 +0000 (GMT) (envelope-from plosher-keyword-freebsd.a36e57@plosh.net) Received: by luftpost.plosh.net (Postfix, from userid 1001) id A9C8732609; Fri, 19 May 2006 23:38:35 -0700 (PDT) Received: from [204.152.187.37] (tardis.isc.org [204.152.187.37]) by luftpost.plosh.net (tmda-ofmipd) with ESMTP; Fri, 19 May 2006 23:38:03 -0700 (PDT) Message-ID: <446EB862.4050102@plosh.net> Date: Fri, 19 May 2006 23:34:10 -0700 User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308) MIME-Version: 1.0 To: freebsd-ports@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBBCE78F5A5CC74751693B805" From: Peter Losher X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) Subject: Questions re: portupgrade & local packages. 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: Sat, 20 May 2006 06:34:59 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBBCE78F5A5CC74751693B805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable So I have been a basic portupgrade user for a couple of years now, and I am starting to roll it out as a more complete package management across all of my personal boxes. However I have come across some roadblocks, and 'man portupgrade' isn't too forthcoming... (or it's too late at night on a Friday evening) If there is a better forum for portupgrade questions do let me know. :) In any case, I have started to build all my own packages that I pull from a internal repository - most with the standard defaults turned on, but some have specific tweaks. For example, I build net/mtr w/o X11 support, and the resulting package is named mtr-nox11-.tgz. All fine and dandy but when I try to 'portupgrade -PP mtr-nox11' I get: -=3D- ** Detected a package name change: mtr-nox11 (net/mtr) -> 'mtr' (net/mtr)= ---> Upgrading 'mtr-nox11-0.69' to 'mtr-0.71' (net/mtr) ---> Building '/usr/ports/net/mtr' [...] -=3D- And then proceeds to try and slurp over a mtr package (which obviously doesn't exist) Is there any way I can tell it (preferably in pkgtools.conf) to not try and detect a name change, and just pull over the mtr-nox11-0.71.tgz package I already compiled? The other roadblock is that I want to keep a /usr/ports/local directory for some internal packages I am testing out. I have already generated a /usr/ports/Makefile.local w/: -=3D- # Adding local ports dir =2Eif ${.CURDIR:M*/ports} SUBDIR +=3D local =2Eendif -=3D- to add the local category, and have generated the ports index via 'make index' Is there a command to compress the INDEX file (I didn't see an option in /usr/ports/Makefile) as it's done on the FTP servers. Also, if I am only installing packages (and using 'portupgrade -PP') on the downstream boxes, should I be able to only have to pull over ports-base, and let portupdate use the INDEX.db to determine if a port needs updating? Thanks in advance - Peter --------------enigBBCE78F5A5CC74751693B805 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEbrhuuffIhmkXw7kRAsjCAKDTTwo4O8KkdA3wJ3/2TZa+2MDgEgCeOM4Y fyon2E0ErrP87i2eN9bqkhM= =9Oql -----END PGP SIGNATURE----- --------------enigBBCE78F5A5CC74751693B805--