From owner-svn-src-projects@freebsd.org Mon Feb 8 11:17:28 2016 Return-Path: Delivered-To: svn-src-projects@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 66B0BA9F6E7 for ; Mon, 8 Feb 2016 11:17:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 498F61E3B; Mon, 8 Feb 2016 11:17:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id A4D7210CA; Mon, 8 Feb 2016 11:17:27 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Mon, 8 Feb 2016 11:17:26 +0000 From: Glen Barber To: Nathan Whitehorn Cc: svn-src-projects@FreeBSD.org, src-committers@FreeBSD.org, Bryan Drewery Subject: Re: svn commit: r295280 - projects/release-pkg/release/packages Message-ID: <20160208111726.GD63576@FreeBSD.org> References: <201602042120.u14LKQ2b026571@repo.freebsd.org> <56B3C34B.1080501@freebsd.org> <56B3C6E4.60907@FreeBSD.org> <56B3C7A3.5000502@FreeBSD.org> <56B3EF97.9040205@freebsd.org> <20160205005113.GD13799@FreeBSD.org> <56B3F5A2.7070600@freebsd.org> <20160205013040.GG13799@FreeBSD.org> <56B82697.4090800@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LTeJQqWS0MN7I/qa" Content-Disposition: inline In-Reply-To: <56B82697.4090800@freebsd.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: svn-src-projects@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the src " projects" tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 11:17:28 -0000 --LTeJQqWS0MN7I/qa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 07, 2016 at 09:24:39PM -0800, Nathan Whitehorn wrote: > Thank you very much for the overview! I had a couple of questions inline, > but please feel free to answer them at your leisure. >=20 > On 02/04/16 17:30, Glen Barber wrote: > > > >>Maybe I missed them? The talks I've seen (e.g. > >>https://www.bsdcan.org/2015/schedule/events/563.en.html) describe some > >>technical problems, the idea that pkg is nicer than freebsd-update (true > >>enough), and that having some more granularity (bind and sendmail separ= ated > >>out, for instance) in installation would be a good thing. That all soun= ds > >>perfectly reasonable and good, but is also pretty nebulous. > >> > >>It would be good have something a little more detailed on what a packag= ed > >>base system actually looks like: what kinds of things would constitute a > >>package? > >Short answer: A set of binaries and libraries upon which the binaries > >require to run. >=20 > So would this imply that, say, ls would be its own package? Or that we wo= uld > have something less granular (so that things like sendmail would be a > package)? It seems like this is something still in flux, so there may not= be > an answer yet. >=20 There is no easy way to answer this, because WITH_*/WITHOUT_* knobs are being taken into account. As I see things now, everything in bin/ and sbin/ would be included in the main, default package unless there is a MK_*=3Dno test in the build. Those would be split into a separate package. So no, ls(1) is not expected to be in its own package, but sendmail(8) is. > >>are those packages (e.g. for sendmail) interchangeable with ones > >>from ports? > >Separate package repositories. Separate package naming scheme. > >Completely independent. > > > >>would the pkg tool be imported into base? > >No. >=20 > Doesn't this complicate the installer tremendously? The install ISOs would > need pkg on them and couldn't be built only from the base system anymore. Yes, this is still being worked out. This should be solvable with a tmpfs(5) /usr/local mount on the ISO, however we cannot enforce a network connection to bootstrap pkg(8). An option is to include pkg(8) as part of the on-disc repository itself. There multiple additional layers of "how are we going to [...]" that tail off of this alone. Glen --LTeJQqWS0MN7I/qa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWuHlGAAoJEAMUWKVHj+KT+GsQAImBVgGP8+wibGl3A6mxTxpS Qk6936OwfT7NN09/RcvbM7IHg6xSLkIKJzSMTghc2/ODSKjvfeRQUs9rXq8hZkCQ x3RsO4cMg+e0QF166wdYg0+9wX4folsIIcdFgJmGWbosI1wHlT2YVOWXDEQ8EbQN DEZw8lXy6h8LlUIIfFdrM1mj0BavqNoSE2yzzwYa7Mm3ePzRd63U4VrAwdwZIBns vJRup33sOe2r1e3J5D+NBWM3Veh235gfNOfGm3ZBJ8R/V0eKfC/LWvR1DI6kX1Q8 6g8F42nECqN67Eo5G+FwjBpobxTfLn5ztQPu1Z/HT+oHmN/xuKP+11/8IK1yIQ1w fNUUVW2pR/MlWKFVj0ds14RVXlzdbFKYGTA/k4rrTM7nZPrEBNpEni1TrmpbM1n5 5xF7oYyuRZ/lLGkNSJvNDESNgrUoNErG27JPvChr3KbojMcq7JYmdfXuu7wpkv2u +9AwogKHVEY0o2A2jiwq76qpgLZyy8DRRvaz9eQwcja4Iuy70OyF7khbAORxZSxJ HSyfFxfBW3ljOfZmQcEbEijw86Uf47oAGwxpAhhz4JlR3AukF/iivPeo6rvr/kC9 QZh5iXN7+QBcfyyvIYpwvdvwVGRlQhbK7oCiOZYUUovutY8w3bS7DpIj/TfqHMs6 3n0zKoshVs5iWNMerdhp =Mdt+ -----END PGP SIGNATURE----- --LTeJQqWS0MN7I/qa--