From owner-freebsd-pkgbase@freebsd.org Tue Mar 15 15:44:08 2016 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 A94EBACA890 for ; Tue, 15 Mar 2016 15:44:08 +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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A5FF1FE7 for ; Tue, 15 Mar 2016 15:44:08 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (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 8CAD37BCC for ; Tue, 15 Mar 2016 12:28:06 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/8CAD37BCC; dkim=none; dkim-atps=neutral Subject: Re: [CFT] packaging the base system with pkg(8) To: freebsd-pkgbase@freebsd.org References: <20160302235429.GD75641@FreeBSD.org> <56E73495.2020600@freebsd.org> From: Matthew Seaman Message-ID: <56E7FFCB.7050008@freebsd.org> Date: Tue, 15 Mar 2016 12:27:55 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <56E73495.2020600@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2umj3wfljbSmfFgPQELI4kDNMMoGTFOI6" X-Virus-Scanned: clamav-milter 0.99 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=2.2 required=5.0 tests=RDNS_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 15:44:08 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2umj3wfljbSmfFgPQELI4kDNMMoGTFOI6 Content-Type: multipart/mixed; boundary="8mGWgvoCEoIeGdS8HGWACGUNwJonVubK8" From: Matthew Seaman To: freebsd-pkgbase@freebsd.org Message-ID: <56E7FFCB.7050008@freebsd.org> Subject: Re: [CFT] packaging the base system with pkg(8) References: <20160302235429.GD75641@FreeBSD.org> <56E73495.2020600@freebsd.org> In-Reply-To: <56E73495.2020600@freebsd.org> --8mGWgvoCEoIeGdS8HGWACGUNwJonVubK8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 03/14/16 22:00, Ren=C3=A9 Ladan wrote: > This leads to the more general > question if/how packages from the Ports Tree should indicate a > dependency on base packages. Something like > "LIB_DEPENDS=3Dlibjail.so:base/libjail" ? (and yes, currently all base > packages have "base" as a single common origin...) How is the ports supposed to fulfil this dependency if it is found to be missing? You'ld either have to fail on a missing base package or rely on pkg(8) to install it -- the latter seems pretty reasonable, but that behaviour is quite an important change to the ports overall behaviour. It gets even more complicated if you need to depend on specific versions of a base package. I think having an attempt to install a port result in triggering an update to a new version of the base system would probably not go down too well. It's an interesting question though. If we're going to record explicit dependencies against the base system in packages, we'd absolutely need the whole variable version number dependency thing that was discussed earlier. You wouldn't want to be forced to recompile / reinstall everything binary if there's any update to the package containing libc, and that shouldn't be necessary in any case due to the forwards compatibility guarantee on libc's ABI. Cheers, Matthew --8mGWgvoCEoIeGdS8HGWACGUNwJonVubK8-- --2umj3wfljbSmfFgPQELI4kDNMMoGTFOI6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJW5//RAAoJEABRPxDgqeTnHy8QAJ+bo/PudzqN2JPyMFaTvizA 4F17JT+7BGZpJWguJFS5X3iUP5NEuFh+yFfofqKOLRX5cQHzwAUHFujcfdsH5NAN eVKNsrGsbWu2tKcj0LcmZV3gUMVGbREiOgzG7nwvpKlZ4lyKhBu9wSv6wCvbOkWA DvfGMcge1mMOn2kSdk2d7bOiD5zLFKB7PURXWhsTpCGyc0MIlmQLm9SUvicjZJMB pGltL3bkFuN7iY0p6VrMAdEWpvF2L8AWCNRgwv9zM2h4Nsaivlmkfm/SH/Gq9Wn2 xdE1DBGjyXl57YoAmpUTO5qyrq54IzluROPNdy+g/KfY/MYF9nyugvBZaJnsPsPE PY0OylCDywfYvssFZotIKjJY+o4WbT2qYQLPitWr2uyjAsSvAZYXbKmTPXml/n5W +GWw34VvkVSfOXVIsJMVnAkAIWdoiLCzLz5IN8ll2tczPv3KOLDwuCymySYBNCkg HMfXqHzZ5W0Z3fABr/qskT830AJoMx6TkYrQl8miSxYImdmDR++k5PNgdVDqZ2JL lcqQHyq941lFlO6gMiFjzrgsYDlO9Fi8acJTJ7C5M/Yk/EBf2r5KiYu/OE4wbhKH gpMLhz1SBCpPncn4KNajPRqRXTzVAE9kjVI5TCy0eGQRPYNwRRe07XQFfb06qE/0 QBunWQckaS2RhD9z/npn =CbJ4 -----END PGP SIGNATURE----- --2umj3wfljbSmfFgPQELI4kDNMMoGTFOI6--