Brian Harring wrote: > On Wed, Apr 22, 2009 at 04:35:37PM +0300, Petteri R??ty wrote: >> Here's an eclass proposal to wrap EXPORT_FUNCTIONS with auto detection >> of functions. This way all eclasses don't have to duplicate the EAPI >> detection code. If people find this useful, I will document it properly >> with eclass-manpages etc. > > Mind you I follow the "Keep It Simple Stupid", but is this really > needed? In other words, how often do people really hit this? > > If it's useful, whatever, but I can see the inverse of the problem > you're trying to solve occuring- folks being told to use autoexport, > then wondering how to block something from being exported... > > Neutral towards it, just seems a bit much imo. > ~harring
betelge...@pena ~ $ grep -l src_prepare /usr/portage/eclass/*.eclass | wc -l 19
signature.asc
Description: OpenPGP digital signature
