On 08/14/2017 03:39 PM, William L. Thomson Jr. wrote: > On Mon, 14 Aug 2017 15:20:26 -0700 > Rich Freeman <ri...@gentoo.org> wrote: > >> On Mon, Aug 14, 2017 at 5:26 PM, William L. Thomson Jr. >> <wlt...@o-sinc.com> wrote: >>> >>> Portage supports sets, but the PMS has no mention. Then there is >>> debate on what they are. Creating so much noise it drowns the bug >>> request and makes it invalid. Despite the need still existing, and >>> PMS lacking anything on sets. >>> https://bugs.gentoo.org/show_bug.cgi?id=624300 >>> >>> Just the needs I have with portage are stalled, marked as invalid. >>> No discussion for inclusion in PMS. Like documenting sets. >> >> Ah, well, that's the main mystery of this thread solved. Thanks. > > That is the tip of the iceberg, not the main problem itself. I have > never been a fan of EAPI, or the resulting PMS, etc. Having been around > before such existed, I do not believe it has helped Gentoo and in fact > maybe the opposite. Why EAPI 0 stuff is in tree, or very old EAPIs. > > Now becoming more real issues rather than just a dislike of EAPI. > I'm unaware of any other way to introduce progressive changes to an API without literally rewriting every ebuild. Versioned APIs are good APIs, and give developers (both inside and outside Gentoo) something they can depend on and, most importantly, predict. If there was just one EAPI, you'd need to consult git log or some other construct to figure out the API version an ebuild was written against.
The fact we still have older EAPI ebuilds is one of manpower and (dis)interest. I don't see anyone trying to prevent (or encourage) EAPI upgrading across the tree. Generally, we wait until a package needs a revbump/version bump and/or has serious breakage (and thus needing a rewrite) before bumping EAPI. Some jumps in EAPI, for simple packages, are painless. Others are a nightmare. I see no other way to support the 1m+ ebuilds that have been written since Gentoo's inception in an unambiguous, reference-able way. In fact, I'd argue if you don't version your APIs, you're not designing them correctly. APIs *will* change; building a version number into the API ensures the consumers of said API are aware of changes. That said, yes, it'd be nice if every ebuild was EAPI 6, but that is a huuuuge amount of work that nobody seems interested in, for questionable gain. The work would just be repeated when the next EAPI is approved. The way it works now is more organic and better representative of the state of Gentoo development, for better or worse. It's good to see you taking part in constructive discussions! That's not intended as sarcasm. I mean it. Thanks for taking part. ~zlg -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
signature.asc
Description: OpenPGP digital signature
