On Friday, January 6, 2017 9:13:20 AM EST Michael Mol wrote: > > The bigger resource drain, I suspect, will come from maintaining new ebuilds > of old packages; as eclass development and maintenance seeks to eliminate > old and buggy code, old ebuilds will need to be dragged along for the ride.
This is already taking place, and has since the first EAPI. I am not opposed to such things, EAPI. But EAPI does lead to what I call "ebuild wheel spinning". Constantly revising an ebuilds internals that may or may not produce much. May not close any bugs, may not change installed files, may prevent future bugs. But does create more work, and why some stuff remains behind all the way back to EAPI=0. It blows me away how some old ebuilds that should be removed, get touched and improved per eclass and other changes. Or things get updated, but not the package itself. Lots of work that produces very little end benefit. Like revising patches for -p1, when they patch may apply fine now with epatch. Modifying -pN of a patch is minor, but still consumes time for very little if any benefit. Patch applied before, patch applies when changed to -p1. What was the benefit for that time spent? -- William L. Thomson Jr.
signature.asc
Description: This is a digitally signed message part.
