Ciaran McCreesh wrote: > On Thu, 20 Dec 2007 12:48:31 +0000 > Steve Long <[EMAIL PROTECTED]> wrote: >> Point is that your filename format restricts it in exactly the same >> manner. So let's just stick with the use cases which /that/ supports, >> which can more easily be supported with the original design and the >> simple restriction people keep asking for. > > Er, the use case is having trivial-as-possible ebuilds for things that > really are purely eclass managed. >
How is having a line that states EAPI=foo in the ebuild any less trivial than putting a -foo at the end of the filename? If anything the latter is more typing - since the EAPI=foo line would probably be in skel.ebuild...
smime.p7s
Description: S/MIME Cryptographic Signature
