pbulk in five steps


1. Prepare a clear system (real one, chroot environment, jail, zone, virtual machine).
Configure network access to fetch distribution files.
Create user with name "pbulk".

2. Fetch and extract pkgsrc. E.g.:

(cd /usr && ftp -o - http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)
(cd /usr && fetch -o - http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)
(cd /usr && cvs -Q -z3 -d [email protected]:/cvsroot get -P pkgsrc)

or using curl, wget, whatever fits.

3. Deploy and configure pbulk tools, e.g.:

sh pbulk.sh -n # native (NetBSD)
sh pbulk.sh -n -c mk.conf.frag # native, apply settings from given mk.conf fragment
sh pbulk.sh -nlc mk.conf.frag # native, apply settings, configure for limited build

4. If configured for limited list, replace the list in /usr/pbulk/etc/pbulk.list
with your list of packages one per line without empty lines or comments. E.g.:

www/firefox
mail/thunderbird
misc/libreoffice4

5. Start it:

/usr/pbulk/bin/bulkbuild


After it finishes, you'll have /mnt filled with distribution files, binary packages, and reports,
plain text summary in /mnt/bulklog/meta/report.txt



Notes

1. It is possible to run unprivileged bulk build.
2. It is possible to use this script to configure distributed bulk builds.
3. More complex configurations possible.

All these cases are not covered here. The script is small enough for understanding.

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.