From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D7F44158042 for ; Sat, 16 Nov 2024 22:34:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 799D3E0998; Sat, 16 Nov 2024 22:33:57 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3244FE0974 for ; Sat, 16 Nov 2024 22:33:57 +0000 (UTC) Date: Sat, 16 Nov 2024 17:33:53 -0500 From: Ionen Wolkens To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Question on ebuild naming/numbering Message-ID: Mail-Followup-To: gentoo-user@lists.gentoo.org References: <28995acc-18ab-476e-a6fb-6d71b2a3c7da@users.sourceforge.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OPT3VFniYdjMftFZ" Content-Disposition: inline In-Reply-To: <28995acc-18ab-476e-a6fb-6d71b2a3c7da@users.sourceforge.net> X-Archives-Salt: dfb25ad4-85d2-4d41-9fee-c0e85ea146e5 X-Archives-Hash: 8018a42ca25d521f0285987b29d507e4 --OPT3VFniYdjMftFZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 16, 2024 at 05:04:43PM -0500, Jack Ostroff wrote: > There's been an update to the gkrellm mailing list about progress on the= =20 > gtk3 conversion.=C2=A0 It seems much of the work is being done in a speci= fic=20 > git branch.=C2=A0 If I want to create an ebuild to track that branch inst= ead=20 > of master, what would be an appropriate numbering of that ebuild?=C2=A0 J= ust=20 > using a different name with 9999 would work - but then those two names=20 > would have to block each other, since I don't think they could=20 > co-exist.=C2=A0 Are there any examples I can look at?=C2=A0 Just adding s= omething=20 > after the 9999 doesn't seem right, nor does something like 9998. If upstream is planning a specific version for that branch, it could be used, e.g. with Qt we do dev-qt/qtbase-6.8.9999 for EGIT_BRANCH=3D6.8, while 6.9999 is Qt6's main development branch. Doing it *before* rather than after can also be useful if don't want that version to come out by default when someone accepts keywords (aka take normal 9999 instead). Not great but fwiw dev-vcs/git did do the "add something after" with git-9999{,-r1,-r2,-r3} for branches maint, master, seen, and next =2E.. not quite sure who needs all these but well ;) with -r3 being the most bleeding edge afaik. One more option would be to make that branch the 9999 default and not bother keeping both. I did that with qutebrowser when it switched to Qt6 until they merged the changes to the main branch. Ultimately it's not super important though, 9999 ebuilds should be considered unsupported and is either only for the maintainers to track changes or at most users that know what they're doing. So some unintuitive versioning isn't the end of the world. And if that version is going to replace the old eventually, I wouldn't do invasive workarounds like a separate package that blocks. --=20 ionen --OPT3VFniYdjMftFZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmc5HdAACgkQskQGsLCs QzSU3Qf/Zvk0UBJ/dkF+5VckWDjKJL8AYxGbd0ti9KacO9zSzirE84pqE24/rw39 zBOVid3eVLFRbC2KijvaS7nFf0ejt/7U9qMR9IGC3VVhAQ09Cjr5gNXACNUcdmnT 1iJtkmytZd+9aZtZTHVU8a0au3CW5XZ/ap15FRsixy4Mcld0WuVH5QA/aH5UuIko bJvQzYOUXlHHOh/AjpXx+z6ZcBIXv0sAzWoFVT+3jgXzQOgsMcUSC2s7H0bfFsqn xp9Vapx85AMdOcoTfZlpkd1WRYd5hLByGIR4u9jlbQSBdFKRYAo/eDkkSPtPiIKb C1+IxFzKOjI/kP5Q+dei8dzLHj5cJA== =+yKT -----END PGP SIGNATURE----- --OPT3VFniYdjMftFZ--