On Tue, 2005-01-18 at 12:33 +0000, Ciaran McCreesh wrote: > On Tue, 18 Jan 2005 05:39:06 -0600 Daniel Goller <[EMAIL PROTECTED]> > wrote: > | considering you called the suggestion "really really stupid insane > | absurd", it seems to be just another hefty ciaranm comment/insult w/o > | any constructive criticism > > Well, think about what you're suggesting. A change to the einfo messages > displayed by, say, vim-plugin.eclass leading to a version bump for every > single app-vim package? Yeah, right.
No, a version bump of vim-plugin-1.2.eclass to vim-plugin-1.3.eclass. So if you accidenally break something I can revert to 1.2 withou doing weird cvs-fu and overlay hacks. The semantic of what needs to be recompiled when an eclass changes need to be defined, but for a "stable" Gentoo it is pretty much neccessary (how else can you "lock" eclasses to have a reproducable configuration?) > | "Version specific code is already doable with versionator. The > | eclasses that need this do it already" erm? As far as I can tell, it solves a different problem. > | if finding a problem involves finding a particular version in cvs, > | then not all that need it use it, so use the more technical sound > | version of taking care of versioned eclasses, dont get personal if you > | know of a technologically enforcable "smart way" of doing it, say it, > | dont' ridicule, be constructive > | > | if all that need it used it, then foo-x.y-rz would still work and only > | foo-x.y-rp was broken, no cvs fishing involved > > No technological solution can possibly be adequate (there's even a proof > for that). The correct way to do it is through developer education, not > insane technological hackarounds. QA tools can at best only provide > suggestions, and they can only catch certain kinds of errors. repoman > isn't an alternative to skilled developers. In this case I'm undecided ... Is it a social or a technological problem? From my point of view it is more on the technological side, but it seems that our understanding of the problem differs. Patrick
signature.asc
Description: This is a digitally signed message part
