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