Date: Fri, 23 Nov 2012 21:26:50 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: Walter Hurry <walterhurry@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: using new pkgng system on 9.0 system Message-ID: <50AFEA1A.1040602@FreeBSD.org> In-Reply-To: <k8omnj$kde$1@ger.gmane.org> References: <50AE3BF5.1000200@a1poweruser.com> <50AE7716.6060506@infracaninophile.co.uk> <k8omnj$kde$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig78573BD520224EF13612C115 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 23/11/2012 20:36, Walter Hurry wrote: > Poudriere though: I read somewhere that ZFS is a prerequisite. Is that = > so?=20 Yes. poudriere uses the cloning and snapshotting abilities of ZFS as a fundamental part of the way it works. You can use tinderbox instead if you only have conventional filesystems, but that isn't so easy to use as poudriere. > Second question: At the moment I'm using 'pkg create' to generate=20 > packages from conventionally built ports, 'pkg repo' to create/update t= he=20 > tarred repo file, and a tiny Python script for HTTP serving. Am I missi= ng=20 > out on some functionality? Convenience mostly. Basically what the package building software does is take the repetitive chore of typing 'make buildpackage' over and over again, and automates it. Pkg repos built 'by hand' have exactly the functionality as those built using poudriere. You only need a very basic webserver to publish the packages, or you can just use a file:// URL and no HTTP server at all if you're creating packages to be used on the same machine. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enig78573BD520224EF13612C115 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 undefined - http://www.enigmail.net/ iEYEARECAAYFAlCv6hoACgkQ8Mjk52CukIxCMwCfRBjEnMPcY9Q1aI0iukVmNdnW Md4AnR88CwwAbIVN8GjIm637EMclRQwi =jjc9 -----END PGP SIGNATURE----- --------------enig78573BD520224EF13612C115--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50AFEA1A.1040602>