Date: Fri, 19 May 2006 23:34:10 -0700 From: Peter Losher <plosher-keyword-freebsd.a36e57@plosh.net> To: freebsd-ports@freebsd.org Subject: Questions re: portupgrade & local packages. Message-ID: <446EB862.4050102@plosh.net>
next in thread | raw e-mail | index | archive | help
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-<version>.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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?446EB862.4050102>