Chris Gianelloni wrote:
Have you ever heard of a header file in C? Consider an eclass to be the same thing. Code that is shared by all of the ebuilds. They are supposed to act the same, not act differently for the same functions. A user should be able to look at games_make_wrapper and know how it will work, not having to worry about how it will work on *this version* of the eclass.
all you get is the same interface, the code behind it you dont know about if you say get a binary only lib, you can check the header to make sure the interface is still intact, what the underlying code is you dont know, but you know the lib you got now has version 1.2 while you last used 1.1, if 1.2 doesnt work (same interface or not) you still have 1.1 and can revert to that,
if the eclass interface is intact but the underlying code does break things , the user doesnt know games_make_wrapper still works or not, he only knows it is still there
if all the fuzz is about games devs and their one finger salutes and people advice me to size my proposal down to system only packages, whch are much moer critical than some game you wouldnt find in a production environment, then im more than happy to do so
same for vim*.eclass
the core thought is to protect the system
i didnt want to cut corners and left it globally in the proposal
focusing on system only is something im more than willing to compromise on, since at this point the resistance seems to come only from non system critical things
i cant talk for patrick there
certainly there were things a production environment would like to have predicatbility for, be it httpd, db, or other usable packages, kernel even since there seems to be interest there too to have versions even if less fine grained than i keep on using it for examples sake, games packages are certainly not one of them, nor is the editor used there that critical that the idea should die on one editor having a heavenly perfect eclass
forget for one moment the idea your eclasses would be affected, and objectively look at what is proposed would create a saner more predicatble system, i think yes, and companies interested in gentoo for their systems would probably also be interested in seeing server packages undergo the same predictability enhancement
i doubt they would turn a nose on gentoo if they get a saner system for their production environment that does not allow them to have the same predictability on games or one editor
i would think they would appreciate the small effort on our part to keep their systems sane, and your avg use Joe Happy would enjoy the same predictable system
signature.asc
Description: OpenPGP digital signature
