Re: [gentoo-dev] install CD bloat

[Jon Portnoy]

On Thu, Aug 21, 2003 at 01:59:19AM -0400, Stewart Honsberger wrote:
> Jon Portnoy wrote:
>
> >Why? The amount of editing done prior to getting your system to a point
> >where you can emerge vim (i.e., after emerge system) is minimal.
> >Offhand, I can only think of make.conf.
>
> make.conf, fstab, hostname are the basics. /install.txt is a
> possibility, though less handles that.

fstab and hostname come after emerge system. You can emerge vim before 
editing them.

>
> >nano is more than enough for editing make.conf. We're trying to _cut
> >down_ on bloat, not increase it.
>
> But if ViM and Perl and the Kitchen Sink libraries are already installed
> on the CD, removing Perl will cut down bloat. ;> It's just a matter of
> degree.
>
> Re: my previous message about limits, if we're doing this solely in the
> interests of cutting down bloat, we could throw a few lines about "echo"
> and stdout redirection in install.txt and forego the editor altogether.
> (Who remembers 'edlin'?)

I think a pager is reasonable, but everyone's favorite editor isn't. I 
could make a case that emacs is just as standard as vi - should we 
include emacs?

>
> >Okay, so merge after emerge system; why do you need it for editing a
> >single file (make.conf)?
>
> Don't underestimate the complexity of editing make.conf. There are
> presently ${VERY_LARGE_NUMBER} of variables to consider in the file, and
> I know my USE="" line is quite long (atleast two wraps at 80 character
> screen width).

Why does any of that involve doing anything that nano cannot do but vim 
can?

-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev@g.o mailing list