Date: Wed, 20 Feb 2013 17:08:18 +0100 From: "Patrick M. Hausen" <hausen@punkt.de> To: "freebsd-stable@freebsd.org List" <freebsd-stable@freebsd.org> Subject: Poudriere questions Message-ID: <2954D7E9-5FBD-4A9E-A097-195F2BBB195E@punkt.de>
next in thread | raw e-mail | index | archive | help
Hello, we use NanoBSD to build the software installations for our hosting = platform and I'm trying to better automate the process of building packages. Poudriere looked like an interesting tool to me, so I tried it. Quite = painless, but two questions currently remain: To me it looks like Poudriere populates the build jail/chroot from = release tarballs fetched from an FTP server - but I'd rather use, say, 8.3p6 as the build platform as well as the one at runtime. At ~300+ installed = ports I simply do not know if anything links statically against base system = libraries and I want to catch all security updates included in RELENG_X_Y. How would I go about that? Second, how do I specify build time options that are not available via = the dialog most ports use for "make config"? Currently we use an ad hoc = shell script that simply installs all the ports I want, and the line for e.g. = Apache reads: cd /usr/ports/www/apache22 && make -DBATCH -DPROXY=3Don -DPROXY_HTTP=3Don = -DSUEXEC=3Don -DSUEXEC_DOCROOT=3D/var/apache = -DSUEXEC_LOGFILE=3D/var/apache/GLOBAL/suexec_log install I can enable all options that simply taken an "on" setting, but what = about the paths for suexec? Obviously they are critical to the operation of = our servers. If this is the wrong list, I can of course take the discussion to -ports = or anything else more appropriate. The Poudriere wiki doesn't mention external ressources besides IRC. Thanks=20 Patrick --=20 punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: J=FCrgen Egeling AG Mannheim 108285
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2954D7E9-5FBD-4A9E-A097-195F2BBB195E>