Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Dec 2015 09:33:40 +0000
From:      Steve O'Hara-Smith <steve@sohara.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Migrating from ports to pkg
Message-ID:  <20151217093340.4de4f38c08dd40ca7bac7cee@sohara.org>
In-Reply-To: <56726B61.9000909@FreeBSD.org>
References:  <CAPi0psvaKXKo-951QWy7_CEKD4yZO3wK8E=gHKu4=eTAqG+4Xg@mail.gmail.com> <5670B7C8.5000603@columbus.rr.com> <56711F73.1020606@FreeBSD.org> <CAPi0psvButCx+0J7tQnYog=WDpN3ohsnACc0R_6F0ix=CbRjrg@mail.gmail.com> <20151216204758.527efa26316df1e337fb136b@sohara.org> <56726B61.9000909@FreeBSD.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, 17 Dec 2015 07:59:29 +0000
Matthew Seaman <matthew@FreeBSD.org> wrote:

> On 16/12/2015 20:47, Steve O'Hara-Smith wrote:
> > 	With poudriere you wind up building all the dependencies locally
> > and so have far more locally built ports than you need. I find poudriere
> > works best if you do all your own package building, otherwise clashes
> > between local and remote built packages are hard to handle.
> 
> I believe Bryan is looking at ways to seed a poudriere build from a
> different repository.

	Essentially automating the manual process I described ? That would
be very nice indeed. If it could automatically track the right ports tree
that would be *wonderful*.

>  It's something I've wanted for quite a while, but
> the systems where I'd like to use it have sufficient capacity that
> building a bunch of packages multiple times[*] isn't a really big deal.

	I went fairly low power (both my workstation and NAS/services boxes
are Atom based - next iteration will likely be ARM) some time ago which has
made me sensitive to compile workload. Updates were quite frustrating until
I discovered pkg lock :)

-- 
Steve O'Hara-Smith <steve@sohara.org>




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20151217093340.4de4f38c08dd40ca7bac7cee>