From owner-freebsd-pkgbase@freebsd.org Fri Aug 11 07:57:45 2017 Return-Path: Delivered-To: freebsd-pkgbase@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96F79DC97C2 for ; Fri, 11 Aug 2017 07:57:45 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 41A59655CD for ; Fri, 11 Aug 2017 07:57:45 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:1c1d:86a1:a200:b700]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 620B210A4 for ; Fri, 11 Aug 2017 07:57:42 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/620B210A4; dkim=none; dkim-atps=neutral Subject: Re: pkgbase update and progress To: freebsd-pkgbase@freebsd.org References: <20170810140615.GD63224@FreeBSD.org> <1218488026.1377609.1502378299872.JavaMail.zimbra@ixsystems.com> <20170810152151.GB82820@FreeBSD.org> From: Matthew Seaman Message-ID: <8eb2fbb1-b9e2-e343-b2ba-fcdaa425c18b@FreeBSD.org> Date: Fri, 11 Aug 2017 08:57:35 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="THqqH3cbVMIJ6kuLTxrgTVaWACh8k50PC" X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 07:57:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --THqqH3cbVMIJ6kuLTxrgTVaWACh8k50PC Content-Type: multipart/mixed; boundary="nIkr1io5DSurveM0X2Gr8PUFdf7nNP8lc"; protected-headers="v1" From: Matthew Seaman To: freebsd-pkgbase@freebsd.org Message-ID: <8eb2fbb1-b9e2-e343-b2ba-fcdaa425c18b@FreeBSD.org> Subject: Re: pkgbase update and progress References: <20170810140615.GD63224@FreeBSD.org> <1218488026.1377609.1502378299872.JavaMail.zimbra@ixsystems.com> <20170810152151.GB82820@FreeBSD.org> In-Reply-To: --nIkr1io5DSurveM0X2Gr8PUFdf7nNP8lc Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 11/08/2017 00:05, Ben Woods wrote: > On Thu, 10 Aug 2017 at 11:35 pm, Matthew Seaman w= rote: >=20 >> On 10/08/2017 16:21, Glen Barber wrote: >>>> * Since we have no mechanism of properly merging changes to /etc >>>> we simply copy files as needed with pc-updatemanager, and it is >>>> difficult to maintain what should be updated, merged, or removed. >>>> >>> This is another long-standing item in the list of things to fix, inde= ed. >> >> The idea floated at BSDCam was to have a package that would install a >> pristine copy of the /etc files under /var/db/etcupdate and prompt the= >> user to then use that tool to update or install their configs. That >> should provide a nice compromise between having the files available fr= om >> pkgs and not enforcing a specific mechanism (tools, not policy) to >> update /etc. >> > I haven't attended either of the conferences, and I'm sure this would h= ave > been discussed, but for those of us who weren't there: >=20 > Pkgng has 3-way merge capability (copied from fossil-scm in pkg 1.4.0).= Why > are we considering using it? Not having ever seen this functionality us= ed, > I would have thought the only things to do would be agree on where the > pristine old copy would be stored (.sample files in /etc?) and perhaps > improve pkgng if the user experience isn't satisfactory. Yes, that is another alternative. At the moment we're all theorising about this it's going to work, but until we can get empirical and start testing some actual code, we aren't going to be drawing any firm conclusions. I think etcupdate(8) has a longer history and people are more familiar with it whereas the 3-way merge code in pkg(8) has been exercised relatively rarely. There's also considerations about how this would fit into various different workflows -- everything from people that only ever download the standard pre-compiled packages for a release, to developers trying to cross-build highly customized embedded systems. Having a 'merge' step that is separated from the 'install' step seems advantageous in that it allows a point where people can substitute in their own alternatives for managing /etc files. Cheers, Matthew --nIkr1io5DSurveM0X2Gr8PUFdf7nNP8lc-- --THqqH3cbVMIJ6kuLTxrgTVaWACh8k50PC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZjWN2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATFIQQAJs4SdkwwZsZ+pDyo/SxIc3N TEAOnMKCIEEtSojNcKy6Jf6NtdM4zXvJ0srhsAHPRCnStaunrJ78YWvXeyOnbHjF Nrm864G5tikHMn9OWX441eTisIgHm9KCW8+R3wr47jgZP4bC4C4tewOX8h1dsCvi 731PTdMYPMbUKyMCRD1Q6ANhxPFfGecRjwkgtu8i4qCccmtuTDWQIxlVIQktNk/D dOMxsK9I6jFsi6b7DpLd6ID/0rwGVD7+fjn54kY0Son8fKz0ogx5R9lYdqEOZW2q wBlbeXHlwfZT1QsL1VysqPMOEaI3Ba79qJQgyH+f88v0nvcMVGg+xD52i7PPykF2 G7SybDd0wIs7XhQ5yOGgUH2tXZMg1se89VkbPmHshD0bD0zkUyRu/yfA6Ko7VM20 ctbe0az4yzt4RNL6RkHFh7mo+FYgF6ZWiLYP/eiRoecFUpsV0973K6BJZGfkVuVX CpKZaJZKxvZug+cc+Q/8QlqdaNyj3hamsVXCKUMu+ckCI5nmLfMsJ/6jmoJ7LFeA d1kBG+HmetuVxlqCUYUIae86svVxvU0tlxm4VsEyt1/osvvA81rLhX9SBSWrrt9F 9xQu1tX8dyaJ7SiSmqjIEUbXsBkZSG2+UhFSkrtYc11X7j0DndL2YxnENxJ+HmHO wuEVfmuwHXsV81bLPE8w =imKQ -----END PGP SIGNATURE----- --THqqH3cbVMIJ6kuLTxrgTVaWACh8k50PC--