Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 93357782AFC for <~alpine/devel@lists.alpinelinux.org>; Sat, 12 Dec 2020 10:38:45 +0000 (UTC) Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1607769525; bh=gmZIvZ1NXtLKNmceHy6VCJnhLckwIWEwm9LykHRpshM=; h=Subject:From:To:In-Reply-To:References; b=JK//iwzKvBhauRbjgSGb5cXQQBviR4oW78oiDV+WSRiEj1hgPrbZfY8nPece3k60y HiHAuMOSkEiYKbTNkKUZ0kHSq2BH6MaI/pvMaNOOEfy3CthasxErusMVpWQZMEavTJ A9Jn/OUUnKH349oBqKZcMlrPI0TgPh27QItuilfns5LsLNeO29+BOY0cYjYZbhMotj ++AY7qi47nx45rkSvP8CBn2xFzR54nk+mgnqFV+72oKm/tvcnASMrkV7dwwlFuFAvZ EoPpyP15YbBxMf4EcN4QWB55X1sCqYG28gKyWHu4atSx5XFuAUHBEjoEfCa3Okyngp 9OlBYUNOWNPNg== Subject: Re: Implement versioned names for major libraries to ease upgrade process From: Rasmus Thomsen To: ~alpine/devel@lists.alpinelinux.org Date: Sat, 12 Dec 2020 11:38:44 +0100 In-Reply-To: <86c7a81e-1640-7f82-9e13-dfdbe1aad07b@gmail.com> References: <86c7a81e-1640-7f82-9e13-dfdbe1aad07b@gmail.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-jgccugsAqQvUUrnnEHtH" Mime-Version: 1.0 --=-jgccugsAqQvUUrnnEHtH Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, On Sat, 2020-12-12 at 06:36 -0300, maxice8 wrote: > Hello, >=20 > Distros like Debian and Void Linux have packages for major version of > libraries include the major version in their pkgname (example:=20 > libboost1.75). >=20 > I'd like to implement that for Alpine Linux. >=20 > ## Benefits to Alpine >=20 > Ease the upgrade process of major libraries with lots of consumers > (like=20 > boost that has 127-ish consumers) by allowing 2 or more versions of a > library to be installed in parallel. Hm, I think the only time users interact with major libraries upgrades are on edge or if they upgrade between major versions. As such I don't think the effort/maintaince overhead versioned libraries introduce is worth it just to not break edge during rebuilds of big packages like boost. One thing that might be interesting about having versioned names for libraries would be that it would make using edge packages on stable releases less broken, but if we only do it for major libraries it'd still be pretty broken for packages which use un-versioned libraries.=20 > [...] > This is already done for llvm which breaks API and ABI every MAJOR=20 > release so we keep llvmN and llvmN+1 and remove llvmN once all > packages=20 > are switched over to use llvmN+1. I think we only do this for LLVM because packages tend to take a long time before they switch over to new LLVM versions because it's so much effort to stay on top of LLVM effort. --=-jgccugsAqQvUUrnnEHtH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEErepJabCshwIJ3OXBERUkFRgVTqYFAl/UnbQACgkQERUkFRgV TqZ9PhAAmgm8NyqH9+4YYiyswPD0gsebmo1i7d9VhgZaXEWSQeitThEYx8/DyJOk TsENKEKpP0rtV8teRMqnE7nRqiDNnRN04PgH7iZuoKn47knga+fW/+gVCheQ0HN1 /jDX3jKReorRxwHQKrE28I8AjuTfJvrwM+wutlIK+E+MpBQg9ko8b0DcU4at4639 Tw9MZyayf4Q/xCb9giqr2gEAud7hfSCOU7K6tU3rSjxEbkbXO7bWEYNo0C71i8b9 XD/us9QKDvSd0ZN2TQydr0vhkyaKnd+8ycY2bWr61qeniJZrv1ICjbEXXUeEpHpW gZyJlAZ6hu3F55MTsU38xnsu0qDCGmBhveAQx/gnRPuGm7/lX8uP5zyyTMc9CD1L N92d57QqnpXw4kBf7LRtSwK2mm3cbig7EHFljlpL0BpFd35rB6iRduZhdjEBPxTI pek84FooJidv/MnlqEMEZKD91iSl5K1SNh+8W5fTcDyR1SOIh8e+k1P72ZwevuyP Yb5+vmsOw2e/KOXt3lWY1EujbKaaCI2pLOWGLwh1kKrPFt2ARnKA1t0c9nG2wt90 Tx76WsamTGW6EfDcK/z8t++/Z1cIIodAUs1SaPavh3SX6wvDxYESMzWG48enHiVi SUQelGUaigxMpjhBfX+/RO+ddyzOnWDbhD5Efmv+IlpwHOFnGVs= =XvL+ -----END PGP SIGNATURE----- --=-jgccugsAqQvUUrnnEHtH--