On 10/05/23 13:40, Harry Schmalzbauer wrote:
Am 10.05.2023 um 12:09 schrieb Guido Falsi:
On 10/05/23 11:44, Harry Schmalzbauer wrote:
...
Since the ammount of machines to deploy massively decreased for me,
and pkgbase seems to be more or less ready ('make packages' left a
beautiful repo), I want to replace my customized installation methods
(transfering all it's features for optional usage).
I don't have definitive answers to the other questions (details
below), but I'd suggest you use poudriere to generate the pkgbase
repos. It has the advantage of only replacing required packages on
subsequent builds, which helps if you happen to update and only a few
files are modified (leverages repeatable builds)
Thanks for the hint!
For building, I used to use a custom buildtools-package too, which
handled cutomer-specific configurations and adaptions (pre-populate
configs into the customer-specific distarchives).
But it also became useless resp. much too much maintenance effort
(hirarchical config-layout and maintaining the tools), since I'm not
responsible for many dozends of individual FreeBSD setups anymore.
I like the concept of src-env.conf very much (as opposed to the one of
poudriere).
Maybe I'm not understanding correctly, but the two are not alternative.
Using poudriere you can specify a src-env.conf file and also have
different src-env files for each jail.
So for what you are doing you could have separate poudriere jails with
src-env files each with a different setup.
this is described here (CUSTOMIZATION section of poudriere(8)
https://man.freebsd.org/cgi/man.cgi?query=poudriere&apropos=0&sektion=8&manpath=FreeBSD+Ports+13.1&arch=default&format=html#CUSTOMIZATION
I'm planning to use whatever FreeBSD uses by default. Currently,
it's bsdinstall(8) I guess (which I never used), but I'm not sure if
it is planned that bsdinstall(8) will be made pkgbase compatible.
I rarely install new machines from scratch, but for now my strategy
has been to perform a classic install and then just dump base packages
over them, removing unwanted packages later.
Crude but works, for my needs. Definitely not acceptable if you want
to automate installing more than one machine at a time. So I have
little insight in this regard.
Intresting method.
Well it was the suggested one to start using pkgbase on a live system:
https://wiki.freebsd.org/PkgBase (Initial setup section)
Is it planned that 'classic install' will simply utilize pkg(1) for
setups from scratch one day?
Can't speak for the developers, I guess yes, but it's just my idea.
--
Guido Falsi <m...@madpilot.net>
