Upgrading ports problem with portupgrade(pkgng)

Matthew Seaman matthew at FreeBSD.org
Sun Dec 23 21:39:21 UTC 2012

On 23/12/2012 21:05, Beach Geek wrote:
> And as I understand,  poudriere must be used instead of portupgrade to
> create packages?

That's not right.

   poudriere is an offline pkg building system, designed to build
   packages in a sandbox, and then create a pkgng repository accessible
   to various client machines.  You can use it locally to maintain a
   single machine, but that's sort of missing the point. It only works
   with pkgng, although I believe you can run it on a non-pkgng machine
   to create a repo for maintaining other pkgng-enabled machines.

   portmaster and portupgrade cover basically the same territory.
   They're designed to maintain the locally installed package set on a
   machine.  To that end, both of them are wrappers around the ports,
   and facilitate installing packages by compiling the relevant port
   source code.  The can also use binary packages, typically from a
   FreeBSD ftp server.  Initially they used pkg_tools packages, but
   both have been modified to work with pkgng packages as well.

   pkgng is a package registry application and a binary package
   manager.  It doesn't understand the ports.  However, if you have
   access to a suitable source of pre-compiled packages you can use
   just pkgng to manage those, and have no need for portmaster or
   portupgrade.  poudriere is intended to provide that 'suitable
   source.' although once the official pkg build cluster gets up and
   running, users should be able to use that instead.



Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 266 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20121223/3a6619e5/attachment.sig>

More information about the freebsd-ports mailing list