| 1 |
On Thursday 23 September 2004 09:37, Marius Mauch wrote: |
| 2 |
> On 09/22/04 Mike Frysinger wrote: |
| 3 |
> > On Wednesday 22 September 2004 07:17 pm, Donnie Berkholz wrote: |
| 4 |
> > > On Wed, 2004-09-22 at 16:49, Ned Ludd wrote: |
| 5 |
> > > > As far as a disable feature how about FEATURES="noautossp" ? |
| 6 |
> > > |
| 7 |
> > > Getting a little picky, but ... |
| 8 |
> > > |
| 9 |
> > > no* FEATURES are awkward, just like no* USE flags. Just have |
| 10 |
> > > FEATURES="autossp" by default, same as ccache is. They can change to |
| 11 |
> > > "-autossp" to disable. |
| 12 |
> > |
| 13 |
> > not picky, there are plans to fix all the 'no*' FEATURES and if we get |
| 14 |
> > the IUSE default stuff ( http://bugs.gentoo.org/show_bug.cgi?id=61732 |
| 15 |
> > ) going, we can get rid of all the 'no*' USE flags too |
| 16 |
> > |
| 17 |
> > that said, what needs to be done here in order to get the ball rolling |
| 18 |
> > ? can we simply put together a function in flag-o-matic which will |
| 19 |
> > check FEATURES and ARCH and gcc, and then just `append-flags |
| 20 |
> > -fstack-protector` ? then in our system packages, just call this |
| 21 |
> > function ...-mike |
| 22 |
> |
| 23 |
> What exactly would that FEATURE do ? If it really only affects CFLAGS I |
| 24 |
> don't see the need for another FEATURE flag at all. We already have ~30 |
| 25 |
> different flags, please lets try to avoid another USE desaster by not |
| 26 |
> adding new flags for trivial stuff. |
| 27 |
|
| 28 |
Seconded. (well, fourthed or something I think) |
| 29 |
|
| 30 |
Any new (and existing) FEATURE should meet at least the following criteria: |
| 31 |
|
| 32 |
1. It enables something |
| 33 |
2. The functionality it enables must be implemented within portage |
| 34 |
3. It makes sense for it to be available for all eternity. |
| 35 |
|
| 36 |
Regards, |
| 37 |
Jason Stubbs |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives