Ciaran McCreesh wrote: > And again, you show that you don't understand what's going on. EAPI is > only specified once except where developers screw up. The GLEP merely > moves the EAPI to being set *before* the metadata is generated, which > removes all the restrictions that having EAPI as part of the ebuild's > content imposes.
So, you are saying if developers screw up, then the EAPI could be specified twice, namely in file name and in file content. But why should we tolerate that? And as I have said before, I don't see why having EAPI as part of the ebuild's content has any restrictions. You can extrace the definition from file content no matter how it is defined using whatever way you like. -- Zhang Le, Robert GPG key ID: 1E4E2973 Fingerprint: 0260 C902 B8F8 6506 6586 2B90 BC51 C808 1E4E 2973 -- [EMAIL PROTECTED] mailing list
