Date: Thu, 8 Dec 2016 09:46:48 -0500 From: George Mitchell <george+freebsd@m5p.com> To: "Kevin P. Neal" <kpn@neutralgood.org>, Baptiste Daroussin <bapt@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org, Daniil Berendeev <pipfstarrd@openmailbox.org> Subject: Re: The ports collection has some serious issues Message-ID: <900ae4ed-9530-b50a-eb4c-5fcba6513295@m5p.com> In-Reply-To: <20161208141427.GA77678@neutralgood.org> References: <c5bc24cc-5293-252b-ddbc-1e94a17ca3a8@openmailbox.org> <20161208122802.5d6dy7hjkkusms7h@ivaldir.etoilebsd.net> <20161208141427.GA77678@neutralgood.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/08/16 09:14, Kevin P. Neal wrote: > On Thu, Dec 08, 2016 at 01:28:02PM +0100, Baptiste Daroussin wrote: >> On Thu, Dec 08, 2016 at 05:16:24AM +0000, Daniil Berendeev wrote: >>> Hello guys! >>> [...] >> Have you considered using things like poudriere that would allow you to build >> your own repository with your own set of packages and options. > > Here's a +2 for poudriere. > [...] I've never been able to complete a poudriere run on my build machine without panicking because I have "only" four gigabytes of memory. (It is likely the machine will get more memory for Christmas, though.) I haven't yet had occasion to try synth. I love portmaster. My build machine is not a production machine, so if the build process goes astray, I can at worst delete all ports and rebuild them all. And portmaster will request all options at the beginning of the run and then quietly build away until it finishes (or breaks). The worst thing about ports for me is really an NP problem: FreeBSD can't possibly test all the option combinations. So I expect to have to do some fine tuning on my own. -- George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?900ae4ed-9530-b50a-eb4c-5fcba6513295>