Bugzilla Bug 230001

doit

ppc64 stable

amd64 stable

On sparc, I built nano thus:
 USE='justify slang spell -ncurses nls unicode' emerge nano
But when I look at the config.h file, I see

/* Define this to disable the justify routines. */
#define DISABLE_JUSTIFY 1
/* Define this to disable the spell checker functions. */
#define DISABLE_SPELLER 1

Is this really correct?  And if so, what good are the spell & justify USE
flags?  I don't much care for USE flags which don't do what they say they do. 
The problem here seems to be that the ./configure script for nano advertises
that it accepts a --enable/--disable-speller option, but apparently it ignores
it.  This is minor, of course, but it still seems wrong because we have USE
flags which don't do what the say they do.

ppc stable

I'll mark sparc stable because it works.  But please clean up the USE flags or
fix the configure script or something for the next go-around on this.  I'm
unlikely to mark any future versions stable unless the USE flags do what they
say they do.  I am not sure how we got a USE=spell, for example, which seems
not to do anything.  (Or maybe it does on other architectures?)

i really havent a clue what you're talking about

if something isnt working, file a bug

Stable for HPPA.

(In reply to comment #5)
> I'll mark sparc stable because it works.  But please clean up the USE flags or
> fix the configure script or something for the next go-around on this.  I'm
> unlikely to mark any future versions stable unless the USE flags do what they
> say they do.  I am not sure how we got a USE=spell, for example, which seems
> not to do anything.  (Or maybe it does on other architectures?)
> 

Whatever I was seeing apparently was an artifact of what I sync'ed to
yesterday.  When I reinstall today and examine config.h (with USE='spell
justify'), I see
==================
/* Define this to disable the justify routines. */
/* #undef DISABLE_JUSTIFY */

/* Define this to disable the spell checker functions. */
/* #undef DISABLE_SPELLER */
===================
as I should.

I don't know what was going on; but whatever it was, it seems today's "emerge
--sync" cured it.  Sorry for the noise, just ignore it.

alpha/ia64/x86 stable