On Sat, Jul 02, 2005 at 01:43:43PM +0200, foser wrote: > On Fri, 2005-07-01 at 18:33 +0300, Dan Armak wrote: > > > calling a function in a global scope is a bad idea. it leads to lots of > > > unneccessary (and timely) computations > > Necessary in the case of kde split ebuilds. Take a look at > > kde-functions.eclass::deprange(). > > So you create functions to do things portage really should do ? Wouldn't > pushing the portage team to finally implement a major feature like > depranges be a better idea ? > > The gnome team has been dealing with these things forever, but we have a > preference for a global solution instead of inventing our own wheel.
*cough* chip in. Kind of tired of hearing of "portage devs ain't doing anything", we _are_ actually attempting improvements, but people seem to be missing a somewhat obvious fact about development of portage. Consider this; if it were easy to implement, one might suspect it would have been implemented already. Nature of the portage code is that the stuff people want (I'm talking about mainly dep syntax expansion, remote crap etc, not tweaks to emerge output) is no longer low hanging fruit, nor has it been for quite sometime. Core problems in the code (design mainally) limit easily pulling off these features that those who don't look in the code think should be a one hour extension. Work is underway to try and fix things so that all of the stuff people have been poking about over the years is low hanging (whether implemented already, or easy to extend and pull off). If you want this stuff, know python or are willing to independantly bootstrap your python capabilities on an actual project, chip in, or pretty much sit back. Bit harsh, but help is needed, not bitching, nor further broken kludges slipped into the tree/portage source instead of trying to fix the actual underlying, _harder_ and further reaching problems. Y'all know FOSS, stuff gets implemented by those with either an explicit interest in a feature, or interest in the general improvement of a project- further effort invested is limited by the amount of time developers can realistically contribute. So... chip in. ~harring
pgpfZwDGAJ10B.pgp
Description: PGP signature
