From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D60F71381F3 for ; Sat, 24 Nov 2012 15:47:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3EF9321C06B; Sat, 24 Nov 2012 15:47:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2C0A321C063 for ; Sat, 24 Nov 2012 15:46:46 +0000 (UTC) Received: from [192.168.1.210] (xx034149246.cipherkey.com [207.34.149.246]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dolsen) by smtp.gentoo.org (Postfix) with ESMTPSA id 5653733D941 for ; Sat, 24 Nov 2012 15:46:45 +0000 (UTC) Message-ID: <1353771994.25128.149.camel@big_daddy.dol-sen.ca> Subject: Re: [gentoo-dev] proposal for consistency between {RUBY,PYTHON,PHP}_TARGETS From: Brian Dolbec To: gentoo-dev@lists.gentoo.org Date: Sat, 24 Nov 2012 07:46:34 -0800 In-Reply-To: <2403742.vl7qeNCzhp@virtuoso> References: <2403742.vl7qeNCzhp@virtuoso> Organization: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-K2+/kjDuId6tg9GYfjVK" X-Mailer: Evolution 3.4.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Archives-Salt: 25fa572c-5586-4bc2-b69c-2f4eb9e96d95 X-Archives-Hash: 14908929c45fb2cb5e7e9ed2f4acb765 --=-K2+/kjDuId6tg9GYfjVK Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, 2012-11-24 at 15:30 +0100, Theo Chatzimichos wrote: > Hello, >=20 > We currently have values like the following: > RUBY_TARGETS=3D"ruby19" > PHP_TARGETS=3D"php5-3" > PYTHON_TARGETS=3D"python2_7" >=20 > I find it confusing, and I would like to propose to keep the same style f= or all=20 > the above values. I personally prefer the ruby one. > Keep in mind that if the relevant teams decide to migrate to some other s= tyle,=20 > it needs an announcement and migration plan. >=20 > Theo +1 for the idea, but: I think format should be python2_7, a simple replace('_', '.') produces the correct version string. If need be it can be extended to minor versions 2_7_3 to get 2.7.3 For ruby19, split in the middle to get 1.9, but what about 110, is it 11.0 or 1.10. =20 For php5-3, what happens if a future package has a digit as part of it's name which is allowed and are in the tree. It looks too much like php5 dash version 3 --=20 Brian Dolbec --=-K2+/kjDuId6tg9GYfjVK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAABAgAGBQJQsOvaAAoJECIU2QoBTxfLPIQH/2ngJENWQ6hErDE0EoLkkmp9 xnsSVIb7CIxKSm4S8ImhGfdILMZ3MoHkw/U8YlaEPdp6X+8BG86ydQWPUHWfVI1p EEnMKL3CrD4HKJpgCUscJXNPxtYoG/OLEkPljQfxmiN50rbNvnPyM3k6Pv6j1wiR rM/4Giqhk7uYioIDo/35eoYdA2wVtRehAbpk/Rioz/aS61afwDurkCjf2GtpoTuL CMiKEJ4VAX5siQCcTpXDUvoVGARRoIukvelfjisOyZE+kD6SXuTJL/0QuGBEPrMi Auai+aCn2u2uVGTMHzGFvGlBBk4fo1l8zmWTESmrSh4zJNkOz8z4qsPCsSSW0lY= =8gu2 -----END PGP SIGNATURE----- --=-K2+/kjDuId6tg9GYfjVK--