Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Mar 2014 09:06:10 +0000
From:      Arthur Chance <freebsd@qeng-ho.org>
To:        David Newman <dnewman@networktest.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Using pkg with build options
Message-ID:  <53314702.8030006@qeng-ho.org>
In-Reply-To: <5330CB20.3090705@networktest.com>
References:  <372190939.49499.1395582789284.JavaMail.mail@webmail12> <20140323150144.029c571e.freebsd@edvax.de> <532F15D8.10403@FreeBSD.org> <20140323185258.e389040f.freebsd@edvax.de> <5330C120.40905@networktest.com> <alpine.BSF.2.00.1403241749220.31770@wonkity.com> <5330CB20.3090705@networktest.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 25/03/2014 00:17, David Newman wrote:
> On 3/24/14, 5:05 PM, Warren Block wrote:
>
>> On Mon, 24 Mar 2014, David Newman wrote:
>>
>>> I'm still quite confused over the migration to pkg.
>>>
>>> I have a mix of 9.2 and 10.0 machines. Most run at least one port
>>> compiled with options.
>>>
>>> Is there a guide to moving these machines to pkg and poudriere?
>>
>> Are they all using ports now?
>
> Yes.
>
>> Then just switch each to the pkg database
>> by adding WITH_PKGNG=yes and running pkg2ng to convert the package
>> information.  After that, continue to use ports as normal.  pkg will
>> keep track of them just like the old pkg_* programs did.
>
> Thanks, that's very helpful.
>
>> Using Poudriere to build binary packages of your own is not required.
>> But if you want to do it, there's a short section on setting up
>> Poudriere in the Handbook:
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-poudriere.html
>
> Part of the appeal of pkg is that package binaries install much faster
> than waiting for 'portmaster -aD' to complete after updating the ports tree.
>
> However, if I understand that poudriere link, it would still build my
> custom packages from ports, and thus there isn't much time savings. Correct?

One thing to note is that by default poudriere uses its own copy of the 
ports tree, not /usr/ports, and that copy is updated by

	poudriere ports -u

If like me you already use a cron job to update /usr/ports you can tell 
poudriere to use the existing ports tree by

	poudriere ports -c -F -f none -M /usr/ports -p default

Last time I looked, this wasn't documented in the man page.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53314702.8030006>