Date: Sat, 25 Feb 2012 19:23:56 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-ports@freebsd.org Subject: Re: portupgrade -> portmaster Rosetta Stone? Message-ID: <4F49354C.1050803@infracaninophile.co.uk> In-Reply-To: <CA%2BE3k93doEmK7YpiZLgBCB5WUmOeCCLLLQBak_-Nx8sGqiafhQ@mail.gmail.com> References: <CA%2BE3k93doEmK7YpiZLgBCB5WUmOeCCLLLQBak_-Nx8sGqiafhQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD28925F900D96247C25C81A3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 25/02/2012 18:21, Royce Williams wrote:
> To ease the transition, does anyone know of a Rosetta Stone table, or
> "portmaster for native speakers of portupgrade"?
It's not too hard to switch. Read the portmaster(8) man page -- most of
the central stuff is actually fairly close to what portupgrade does.
A few differences:
portmaster foo/bar
will update anything foo/bar depends on, that is out of date (a bit like
portupgrade -R), and it will always reinstall the foo/bar port.
portmaster -r foo-0.99
will update anything out of date that depends on the foo-0.99 port.
When you get a shlib-bump, a common idiom is:
portmaster -fr libfoo-1.0
which forces an update of everything that depends on libfoo-1.0.
One important difference is the -R flag -- in portupgrade, that means
'recurse through what this port depends on,' which doesn't have an
equivalent flag in portmaster because that's the default behaviour.
Instead, to portmaster, -R means 'restart a previously interrupted
session from where you got to before.'
If you want portmaster to completely ignore a port, touch
/var/db/pkg/foo-0.99/+IGNOREME -- there's no arrays of ports to do
special things with as there are in portupgrade.conf
portmaster doesn't save old shlibs in /usr/local/lib/compat/pkg by
default -- you have to use the -w flag for that, or a setting in
portmaster.rc portmaster doesn't need you to be continually running a
command like pkgdb as it does a pretty good job of keeping everything
consistent just as it goes along. If you get messages about 'malformed
dependency' you should try 'portmaster --check-depends' to clear it up.
But all you really need to know is that for routine updates, first
update your ports tree using portsnap or csup or banging two rocks
together or whatever your favourite method is and then just run
'portmaster -a' Answer anything it asks you, and then sit back and
watch it go to work.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enigD28925F900D96247C25C81A3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9JNVMACgkQ8Mjk52CukIxpnQCghPLozWMTaxq/UOe8DpzXDqRZ
T+cAniHsXMqXzN5cm5eWWa4wZp1YKD0+
=JoUs
-----END PGP SIGNATURE-----
--------------enigD28925F900D96247C25C81A3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F49354C.1050803>