From nobody Wed May 10 12:04:30 2023 X-Original-To: pkgbase@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QGYc83rllz49p99 for ; Wed, 10 May 2023 12:04:40 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QGYc837VCz3HG9 for ; Wed, 10 May 2023 12:04:40 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4QGYc23GNVz6sqB; Wed, 10 May 2023 14:04:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :subject:subject:from:from:content-language:references:date:date :message-id:received; s=bjowvop61wgh; t=1683720272; x= 1685534673; bh=LhwOMZTKlY2xZ1ovZlpQV1r8TVBEQZHIWtP6sD6xOcE=; b=f i6+eKsfPuOrZqIVgFQDD7tGOWImGTY7jZLb/Jax90uG6RvJD6T4tOhTLUIHLcAjU x51Np5ofd0iKuS4E3OQ2TN59c90aPPkgf2MSVfZyqFTti7zyck0vkeYXrztO/piZ 8fuRb4zQ0lrcGoCUkic1pQmP8BtonVr9tAS5K+5mT8VrWtJeshFGpZ13vJh8AYOv j74CvFKRgiBoh3u7BLxSaZKf8bsMiMGqzLMShT51OqEBFT+IeqPGWqZuDLmyj0SW y7qqJjD3rloRMMzy9crEyzaRgQ6ikhU9/YR+FoqQ8C8K3jpb3xMH4B78dmOCJL1Q tooKp7dS3YxHFh/RNuTKQ== Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id VMwVURWJm9BL; Wed, 10 May 2023 14:04:32 +0200 (CEST) Message-ID: Date: Wed, 10 May 2023 14:04:30 +0200 To: Harry Schmalzbauer , pkgbase@FreeBSD.org References: <81e4426a-7b8f-f84a-f201-0892f460c2b8@omnilan.de> <4f8e6e12-e13e-2f06-c039-93c773627693@madpilot.net> Content-Language: en-US From: Guido Falsi Subject: Re: What setup method is planned for pkgbase? In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QGYc837VCz3HG9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@freebsd.org 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