a few short observations on latest BB

Robert P. J. Day rpjday at mindspring.com
Wed Mar 1 02:19:00 PST 2006


  first (and most pedantically), when you originally install the
source and do your first "make *config", every single option is
labelled as "(NEW)", simply because there is no previous record of it.

from scripts.config.conf.c:

=================================
static void conf_askvalue(struct symbol *sym, const char *def)
{
        enum symbol_type type = sym_get_type(sym);
        tristate val;

        if (!sym_has_value(sym))
                printf("(NEW) ");
...
=================================

  but labelling everything as NEW is not all that informative that
first time, and doesn't follow the tradition of the linux kernel in
*not* doing that.  would it be a big deal to add an extra conditional
to not label everything as NEW if there's no existing .config file?

  next, there doesn't appear to be any difference in either selecting
or not selecting "Feature-complete libbusybox".  both generated shared
lib files that turn out to be exactly the same size.  the only
difference is that selecting the full featured library creates an
extra hard link in the install directory but that's it.  based on the
help message, that's not what i expected.  what difference *should* i
have seen?

  next, under "Installation Options," the selection of "Don't use
/usr" might benefit from a slightly more expressive help message to
explain what that option really represents, for the sake of newbies
who don't know what it means.

  just my $0.02.

rday


More information about the busybox mailing list