Michael Orlitzky wrote: > All this is to say that "easy to read" is in the eye of the beholder. > For ebuilds in the tree, the beholder is usually the maintainer, which > is why I think the choice should be left up to him.
I think what mgorny says is that locality of ebuilds is an important factor. > Our ebuilds are bash programs, and in source code, "as little > duplication as possible" is a strong contributor to "easy to read." Here's an idea: Could a little bit of automated (but obviously checked!) de-duplication be made [an optional] part of adding an ebuild into the tree, and please everyone? //Peter
