Ciaran McCreesh <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Wed, 19 Dec 2007 00:06:53 +0000:
>> And if a particular ebuild uses features from a non-conflicting >> super-set of several such EAPIs (Ulrich's message) ... > > Then there should be an EAPI defined that permits all of those features. > > Functionality would only be removed from EAPIs for specific reasons: > > * Conflicts with new features (think *DEPEND vs DEPENDENCIES). In which > case, you can't mix features between EAPIs anyway. > > * Deprecating old nasty features. In which case, you shouldn't be using > said features anyway. > > * Massively different EAPIs. In which case you reaaaallly can't mix > EAPIs. I thought it worthwhile when I saw the question asked, but given your experience in the matter and the lack of anyone from the other PMs saying otherwise, I'll take your word for it. Thanks. (Of course I can't/don't speak for the original question poster.) (BTW, saw the http://obsethryl.eu interview. While I'm probably part of the "noise", someone with the demonstrated tenacity to follow thru as you do... every comment gets a reply... that deserves and gets a lot of respect, in my book. Thanks /for/ that follow-thru.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [EMAIL PROTECTED] mailing list
