Date: Sat, 9 Aug 2014 16:46:57 -0400 (EDT) From: doug <doug@fledge.watson.org> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: pkg-register question Message-ID: <alpine.BSF.2.11.1408091638580.96880@fledge.watson.org> In-Reply-To: <53E66AE4.7040004@infracaninophile.co.uk> References: <alpine.BSF.2.00.1408091325180.41601@bucksport.safeport.com> <53E66AE4.7040004@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 9 Aug 2014, Matthew Seaman wrote: [cut] > That's not really the intended use for pkg-register. It takes a > previously written +MANIFEST which describes some software that has > already been installed on a system and inserts the data from the > +MANIFEST plus checksums etc it calculates from the installed files into > the package database. The +MANIFEST is the 'metadatafile' the man page > is talking about. > > Before staging, this was the way the ports operated. Now, with staging, > you use the very similar pkg-create to build a package from the staging > area, and then simply install that package. Not sure what the long term > plans are for 'pkg register' but making it obsolete in the future > probably should not be discounted. Thank you that was exactly the information I was seeking > What you probably wanted was 'pkg convert' -- or in fact, the pkg2ng > script which is basically a wrapper around pkg convert. Excellent - thanks again
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1408091638580.96880>