Thanks Petteri, > > 1) Status quo > - does not allow changing inherit > - bash version in global scope > - global scope in general is quite locked down
lets move on! > > 2) EAPI in file extension > - Allows changing global scope and the internal format of the ebuild > a) .ebuild-<eapi> > - ignored by current Portage > b) .<eapi>.ebuild > - current Portage does not work with this > c) .<eapi>.<new extension> > - ignored by current Portage 2 a) and 2 c) are fine by me. > > 3) EAPI in locked down place in the ebuild > - Allows changing global scope > - EAPI can't be changed in an existing ebuild so the PM can trust > the value in the cache > - Does not allow changing versioning rules unless version becomes a > normal metadata variable > * Needs more accesses to cache as now you don't have to load older > versions if the latest is not masked > a) <new extension> > b) new subdirectory like ebuilds/ > - we could drop extension all together so don't have to argue about > it any more > - more directory reads to get the list of ebuilds in a repository > c) .ebuild in current directory > - needs one year wait no thanks. > > Regards, > Petteri regards Thilo
