The ports collection has some serious issues
FreeBSD at ShaneWare.Biz
Wed Dec 14 08:06:17 UTC 2016
On 13/12/2016 06:01, Julian H. Stacey wrote:
>> I would say this rarely happens with the default setup, the more port
>> options you change the more likely it is something will break.
> Yes, I now start: cd /var/db/ports; mv * MV/* ; setenv NO_DIALOG=YES
> Before: cd /usr/ports; make BERKLIX_CLIENT=YES # Uses ports/*/Makefile.local
> (still innumerable breaks of course on 1200 ports inc deps.)
> I can re-enable options for a 2nd pass rebuild for the very
> few ports need it (maybe some better way?).
That's what I like about poudriere, one port can fail and builds still
continue until as much is built as possible. I also know that
everything is built before changing anything that is installed.
> poudriere's `-f' is nice to accept a list.
> But I havent found a way to build my list yet from my Makefile.local eg
> cd /usr/ports; make BERKLIX_CLIENT=YES echo_my_category_and_port
> I'll probably hack bsd.port.mk & bsd.port.subdir.mk
To create a list of ports I have installed I just use
pkg info -aqo | sort > myports.list
For setting options, I created /usr/local/etc/poudriere.d/mypkg-make.conf
and filled it with lines like
DEFAULT_VERSIONS= apache=2.4 perl5=5.20 pgsql=9.5
OPTIONS_SET= OPTIMIZED_CFLAGS CPU_OPTS SIMD MMX SSE SSE2 SSSE3
x11-servers_xorg-server_SET= DEVD SUID
then I use
poudriere bulk -j 10stableamd64 -p myports -z mypkg -f myports.list
that way these settings are only used when building my pkg repo and not
when I test build any ports (use poudriere.d/make.conf for settings to
be used in all poudriere builds).
My /etc/make.conf only contains -
so the same setting are used for any manual port builds as well as my
poudriere created pkg repo.
FreeBSD - the place to B...Software Developing
More information about the freebsd-ports