Date: Thu, 5 Oct 2017 09:58:47 +0200 From: Franco Fichtner <franco@lastsummer.de> To: Eugene Grosbein <eugen@grosbein.net> Cc: Adam Weinberger <adamw@adamw.org>, "Michael W. Lucas" <mwlucas@michaelwlucas.com>, ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <3183A82D-0425-4B57-8A12-B72A88892C62@lastsummer.de> In-Reply-To: <59D5E3A0.8030608@grosbein.net> References: <20171004161649.GA51883@mail.michaelwlucas.com> <B2B3E5C7-C9B0-4B6D-86CE-312D1F165DCD@adamw.org> <59D5E3A0.8030608@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5. Oct 2017, at 9:47 AM, Eugene Grosbein <eugen@grosbein.net> = wrote: >=20 > On 05.10.2017 08:14, Adam Weinberger wrote: >=20 >> Poudriere wants to be everything to everybody >=20 > First poudriere will have to learn how to run without noticeable = overhead > compared to "just build from ports" before it could became "everything = to everybody" > and it needs to became part of base system for that purpose. For OPNsense we broke down the poudriere approach into a simple equivalent that is capable of building inside a jail, resume after a faulty build and wrap everything into a ready to use (pkg-repo creation and signing) archive that can be moved to a remote location and unpacked to be used as an online package repo, but it would also work on a singular system. https://github.com/opnsense/tools/blob/master/build/ports.sh In case someone feels the need to know this before starting from scratch trying to build something simple. It does not support clever multi-threading, but then again it would work as anyone would use the ports tree manually and runs well in a headless mode setting via cron for nightly rebuild fun. Cheers, Franco=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3183A82D-0425-4B57-8A12-B72A88892C62>