CFT: FreeBSD Package Base

[kris at ixsystems.com]

This should be very doable with this package base. We use it for FreeNAS in a similar manner, where we disable a couple dozen things from base, resulting in a much more stripped down userland-base package. By default we also break out the doc/tests/debug bits into their own userland-* packages, for same reasons, to keep image nice and small.

-- 
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking TrueNAS M-Series -
Enterprise Storage & Servers Driven By Open Source

-----Original Message-----
From: Lev Serebryakov <lev at FreeBSD.org> 
Sent: Monday, April 29, 2019 9:20 AM
To: kris at ixsystems.com; freebsd-current at freebsd.org; freebsd-pkgbase at freebsd.org; freebsd-hackers at freebsd.org
Subject: Re: CFT: FreeBSD Package Base

On 28.04.2019 22:52, kris at ixsystems.com wrote:

> I'm pleased to announce a CFT for builds of FreeBSD 12-stable and 
> 13-current using "TrueOS-inspired" packaged base. These are stock 
> FreeBSD images which will allow users to perform all updating via the 'pkg' command directly.
> Rather than trying to answer all questions in this announcement, we've 
> created a FAQ page with more details. Please refer to this page, and 
> let us know if you have additional questions that we can include on 
> that page going forward.
 Is it too coarse, isn't it?

 I'm not very interested in packetized base for "big servers" which contains full FreeBSd installation, but I have several NanoBSD installations, which have more than 100 "WITHOUT_XXX" options in src.conf. I want to have packetized base to create such images via `pkg'
Not all these options could be converted to packages, options like WITHOUT_KERBEROS is more build option, but about 2/3 of these options turn off some file-based features, like sendmail, PPP, toolchain or bzip2.

 IMHO, to be really useful packets in base should be based on these src.conf options to have ability to skip unneeded "optional" base components (including, for example, man pages!).

 And one more, not covered with src.conf WITHOUT_XXX: static libraries and header files, of course!

--
// Lev Serebryakov