Gentoo Archives: gentoo-dev

From: Federico Ferri <mescalinum@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: GLEP 55 Version 2
Date: Sun, 07 Jun 2009 12:40:55
Message-Id: 4A2BB553.50709@gentoo.org
In Reply to: [gentoo-dev] Re: GLEP 55 Version 2 by Ulrich Mueller
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Ulrich Mueller wrote:
5 >>>>>> On Sun, 07 Jun 2009, Steven J Long wrote:
6 >
7 >> I'd just like to know what the implications would be for users if we
8 >> kept the .ebuild extension, and a new PMS were rolled out stating
9 >> that the mangler were allowed to find the EAPI without sourcing (and
10 >> giving the restrictions) once portage 2.2 was stable, or the ability
11 >> to handle this backported to 2.1.6, and issued in a release?
12 >
13 > Even if we do only a one-time change of the file extension, can we
14 > ever get rid of the old extension?
15 unfortunately, no.
16 > Or are we then stuck with two
17 > extensions in the tree until the end of time?
18 > Let's assume for the moment that we change from ".ebuild" to ".eb".
19 better put this new ebuild type in a new tree; such a massive change
20 to the tree its not recommended.
21 > Then we obviously cannot change all ebuilds in the tree to ".eb",
22 > otherwise old Portage versions would see an empty tree and there would
23 > be no upgrade path.
24 leaving actual ".ebuild"s as they are now (good healthy state :)) and
25 making new development of ".eb" ebuilds happen in a new tree (I said
26 new tree, but it could be any way that hides those new ebuild to OLD
27 package managers) would help.
28
29 only newer versions of package managers are required to support this,
30 that is they will look for .eb (in new or current tree, not sure
31 what's best) and then for .ebuilds, and ideally this should be
32 transparent to old package managers and allow an upgrade path.
33
34 - --
35 mescalinum@g.o
36 -----BEGIN PGP SIGNATURE-----
37 Version: GnuPG v2.0.11 (GNU/Linux)
38 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
39
40 iEYEARECAAYFAkortVIACgkQV/B5axfzrPsTiACeJCJb3F8Up/+CjHIwC3Slhn/6
41 yZgAoLcJgNn2d3W/JeZPkK85arUPW9vV
42 =fR4T
43 -----END PGP SIGNATURE-----