From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-57395-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 0C72B138492
for <garchives@archives.gentoo.org>; Mon, 14 Jan 2013 20:24:36 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 9B3EA21C067;
Mon, 14 Jan 2013 20:24:22 +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 CEEF521C011;
Mon, 14 Jan 2013 20:24:20 +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 (joses mo46) (RZmta 31.12 AUTH)
with ESMTPA id D004fbp0EJwPnT ; Mon, 14 Jan 2013 21:24:18 +0100 (CET)
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New, shiny EAPI=5 profiles: volunteer, procedure, preparations
Date: Mon, 14 Jan 2013 21:24:16 +0100
User-Agent: KMail/1.13.7 (Linux/3.4.9-gentoo; KDE/4.9.97; x86_64; ; )
References: <201301122147.26044.dilfridge@gentoo.org>
In-Reply-To: <201301122147.26044.dilfridge@gentoo.org>
Cc: gentoo-core@lists.gentoo.org
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="nextPart3830665.xKH2U0lsdX";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201301142124.16674.dilfridge@gentoo.org>
X-Archives-Salt: ea873a3b-58b1-49b7-9163-3f7a830d9384
X-Archives-Hash: 5fc76059d52f5235048bee63b2945c89
--nextPart3830665.xKH2U0lsdX
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
[CC'ing this to core so noone can complain afterwards.]
Since 48h did not lead to any responses positive or negative, I'll start=20
implementing the procedure as given in the original e-mail (quoted below).
As also said below, each arch will get a mail before I touch their profile=
=20
tree and after I've finished.
Cheers, Andreas
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/
--nextPart3830665.xKH2U0lsdX
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)
iEYEABECAAYFAlD0aXAACgkQ3ao2Zwy3NWqdgwCfZKI6ucNVf6IoiF//MICfU2oM
ff4AnjDVpawSi9W3pI8z5GXeG/xW/0CM
=kTFI
-----END PGP SIGNATURE-----
--nextPart3830665.xKH2U0lsdX--