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 E365D13894E for ; Sat, 9 Feb 2013 22:30:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F20A421C05D; Sat, 9 Feb 2013 22:29:57 +0000 (UTC) Received: from mo-p05-ob.rzone.de (mo-p05-ob.rzone.de [81.169.146.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C3EBC21C057 for ; Sat, 9 Feb 2013 22:29:56 +0000 (UTC) X-RZG-AUTH: :IW0NeWCpcPchHrcnS4ebzBgQnKHTmUiSF2JlOcyz+57jTVMtVX7771HX5w== X-RZG-CLASS-ID: mo05 Received: from pinacolada.localnet (95-130-165-88.hsi.glasfaser-ostbayern.de [95.130.165.88]) by smtp.strato.de (josoe mo5) (RZmta 31.14 AUTH) with ESMTPA id Y0198bp19LBePJ for ; Sat, 9 Feb 2013 23:29:45 +0100 (CET) From: "Andreas K. Huettel" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] New, shiny EAPI=5 profiles: volunteer, procedure, preparations Date: Sat, 9 Feb 2013 23:29:45 +0100 User-Agent: KMail/1.13.7 (Linux/3.6.11-gentoo; KDE/4.10.0; x86_64; ; ) References: <201301122147.26044.dilfridge@gentoo.org> In-Reply-To: <201301122147.26044.dilfridge@gentoo.org> 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 Content-Type: multipart/signed; boundary="nextPart1740656.shkJZRnExT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201302092329.51993.dilfridge@gentoo.org> X-Archives-Salt: 9dfd5792-715f-4937-977f-340eb2313a77 X-Archives-Hash: 642b51488f57c1933b0441d371b12f55 --nextPart1740656.shkJZRnExT Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable =46or your information, in the default/linux tree * all 13.0 profiles have been created and are marked stable the same way as= =20 10.0 was * all 10.0 profiles have been removed from profiles.desc * all 10.0 profiles have been deprecated IMHO the waiting time of 1 year decided by Council starts now before we can= =20 remove the 10.0 trees. Maintainers of profiles outside default/linux (e.g. hardened and prefix),=20 please take care of the migration to EAPI=3D5 on your own. Everyone else, have fun! :) Am Samstag, 12. Januar 2013, 21:47:18 schrieb Andreas K. Huettel: > Hi everyone, >=20 > since Council has approved the creation of a fresh set of EAPI=3D5 "13.0" > profiles, I would like to volunteer for creating them. The proposed > procedure is outlined below in detail, and I'd be happy for comments. > [If anything below deviates from Council decision, please tell me- not my > intention.] >=20 > One general question comes first, though: Right now, the releases/10.0 > profile directory does the following things: > * mask too-old portage > * set eapi > * add USE=3Dbzip2 >=20 > Is there anything unrelated to EAPI=3D5 that absolutely must be added to = the > new releases/13.0 directory in addition in your opinion? (Whether this is > the right place and was the right place in the beginning for USE=3Dbzip2 = is > another question.) >=20 > ### >=20 > The procedure (all paths relative to profiles): >=20 > 1) create directory eapi-5-files, with eapi (containing 5), skeletons for > package.stable.mask etc and a readme >=20 > 2) copy releases/10.0 to releases/13.0, in releases/13.0: > * increase required portage version > * additionally inherit ../../eapi-5-files > * other changes as per question above? >=20 > 3) for each arch in default/linux, > * announce on arch alias (to prevent overlapping commits) > * copy default/linux/${arch}/10.0 to default/linux/${arch}/13.0 and > * change inheritance in the new copy to inherit ../../../../releases/13.0 > instead of ../../../../releases/10.0 > * announce on arch alias (so future changes go into 13.0 tree) > [This describes the simple case. I realize that there are differences in > the directory structure, e.g. powerpc/ppc64/10.0, which is why this step > needs extra care.] >=20 > 4) edit profiles.desc and copy all "10.0 lines" to "13.0 lines", with an > initial setting "dev" (if dev or stable before) or "exp" (if exp before) > This makes repoman check against the new profiles when using developer > profiles. >=20 > 5) announce the state on the dev list, urging devs to update their symlink > manually and !test! >=20 > 6) wait one / two weeks >=20 > 7) in profiles.desc, mark all 13.0 profiles stable that were stable in > 10.0, and remove the lines for the 10.0 profiles. This makes eselect > profile now only offer the new ones, and repoman test by default against > 13.0 profiles. >=20 > 8) mark all 10.0 profiles as deprecated by creating a "deprecated" file > (containing the replacement suggestion) in the directory. This makes > portage warn users to upgrade (suggesting a new profile for them), and > repoman ignore the 10.0 profiles. >=20 > 9) long waiting time as decided by Council >=20 > ### >=20 > Everything that does NOT use/inherit 10.0 will remain unaffected, and > whoever responsible may have to take care of that some time before (in > step 10) the main profile directory becomes EAPI=3D5. This means e.g. > hardened, ulibc, prefix or bsd. >=20 > Cheers, > Andreas =2D-=20 Andreas K. Huettel Gentoo Linux developer=20 dilfridge@gentoo.org http://www.akhuettel.de/ --nextPart1740656.shkJZRnExT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEABECAAYFAlEWzd8ACgkQ3ao2Zwy3NWrSBQCfa7873hiSDu4sgvfYZciNYvXd BSwAmwXuFyyrCiyhbawrZ5zDqQtgBarG =ZVAP -----END PGP SIGNATURE----- --nextPart1740656.shkJZRnExT--