Mail Archives: cygwin-apps/2001/11/03/19:00:31
-----Forwarded Message-----
> From: Joshua Franklin <joshuadfranklin AT yahoo DOT com>
> To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
> Subject: Re: cygwin-apps Digest 2 Nov 2001 18:46:34 -0000 Issue 223
> Date: 03 Nov 2001 11:30:25 -0800
>
> > That said, Joshua, can you visit the current
> > setup.ini (I suggest
> > reviewing it by hand) and identify (based on Earnies
> > previously linked
> > email) a good core list of packages that should auto
> > install?
> I'll go ahead and attach my setup.ini
> which works great on my machine (Win2k SP2).
> The only things I did are changed the dependencies of
> vim and which (see below) and switched
> the packages into either "Base" or "Libs" depending. I
> don't like the fact that the
> auto-installed stuff in "Base" is hidden at first, but
> the dependencies are shown (it looks
> like the only things you're getting are libncurses5,
> etc). Also the scrollbar is invisible at
> first even though the packages extend below the bottom
> of the window.
> I'd rather the base be automatically shown and
> dependencies hidden, but since I'm not doing the
> work I'll shut my mouth. (er..stop my fingers?)
>
> > I think the important question is:
> > if I as a new user grab setup.exe, run it, and just
> > click next 7 times,
> > what do I end up with?
> The mad clicker will get a workable system.
>
> > Please follow the following guidelines:
> > 1) Don't include packages simply because a different
> > package requires
> > them. (Requires: clauses handle that).
> > 2) If setup.exe does something that needs the
> > package there, then the
> > package is essential.
> > 3) If a user expects it *no matter what* then it is
> > a reasonable
> > candidate.
> >
> > If you can drop a list of what needs changing to
> > this list, I'll give it
> > a once over, and so can every one else here, and all
> > things going well
> > we can tidy up setup.ini and release this beast.
>
> Absolutely required by setup.exe:
> bash
> cygwin
> fileutils
> sh-utils
>
> If you don't install these packages, you will get
> errors about
> bash.exe, cygwin1.dll, mkdir, or id
>
> A "minimal user installation", list furnished by
> Earnie Boyd.
> http://www.cygwin.com/ml/cygwin/2001-02/msg01111.html
>
> My additions are unzip, zip, login, and texinfo (the
> GNUish man pages always say to try "info foo").
> I wouldn't see any problem with adding a couple other
> things like less (though man already grabs it), tcsh
> for BSDers,
> and rxvt for those stuck on Win9x but want a
> scrollbar. This category could be called
> "Core" or "Standard" and should be installed by
> default for a new installation:
> ash
> bash
> bzip2
> clear
> cygwin
> diff
> file
> fileutils
> findutils
> gawk
> grep
> gzip
> login
> man
> patch
> sed
> sh-utils
> tar
> texinfo
> textutils
> time
> unzip
> which
> vim
> zip
>
> These are automatically downloaded to support the
> above packages; they could be moved from "Base" to
> "Libs" if not already there:
> gettext
> groff
> less
> libncurses5
> libncurses6
> readline
> termcap
> terminfo
>
> If anyone's interested, this will result in a ~40MB
> c:\cygwin tree.
>
> A note about texinfo: if you try to invoke it like
> "info ls", it complains:
> "info: dir: No such file or directory".
> But if you do "info -f /usr/info/fileutils.info", that
> works.
> In my regular cygwin installation, I've got a file
> called /usr/info/dir, but it only has
> TeX information in it and apparently only the autoconf
> and teTeX-beta packages
> provide these top-level "info/dir" files. I don't know
> too much about info, but it would
> probably be good to have a global top-level "info/dir"
> file included in the texinfo
> package so it works OOTB (or at least something about
> how to create one).
>
> A note about vim:
> libncurses6 and gettext need to be added to requires
> in setup.ini
> Also, any thoughts about making a smaller /bin/vi that
> doesn't do syntax highlighting
> or windowing and doesn't depend on the 8MB of
> /usr/share stuff? IIRC, vim when invoked as
> vi acts pretty much like this anyway.
>
> A note about which:
> The requires line for which looks like this:
> "requires: ash cygwin jpeg zlib"
> It seemed to work fine when I removed jpeg and zlib,
> but maybe there's something I don't know
> about how which works internally (but jpeg?)
>
> Hope this helps.
>
> __________________________________________________
> Do You Yahoo!?
> Find a job, post your resume.
> http://careers.yahoo.com
- Raw text -