Ciaran McCreesh wrote: > On Fri, 21 Dec 2007 11:51:03 +0800 > Zhang Le <[EMAIL PROTECTED]> wrote: >> That's the problem about the agreement between PM and ebuild. >> >> If this is agreed upon >>>>>>> import vim-spell using language="en" >> You should be able to get it. >> >> If not, then blame the ebuild writer. There is no problem with the >> agreement. > > Uh... It's not agreed upon currently.
It is not about whether it is agreed upon currently. As long as there is an agreement in any given point of time, it is OK. Such as, put your EAPI definition on the first line of your ebuild, like EAPI="value" >>> Bear in mind that >>> package managers can only use what's been agreed upon at the time >>> they were released, not what might be agreed upon later -- and yet >>> they need to be able to extract the EAPI from anything agreed upon >>> later. >> Exactly my point. > > So we all agree that suffixes are the solution, since they solve this > problem and in-ebuild-content restrictions don't. Good. No, quite contrary. See above. -- Zhang Le, Robert GPG key ID: 1E4E2973 Fingerprint: 0260 C902 B8F8 6506 6586 2B90 BC51 C808 1E4E 2973 -- [EMAIL PROTECTED] mailing list
