This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: cygwin-apps Digest 2 Nov 2001 18:46:34 -0000 Issue 223


On Sun, 2001-11-04 at 03:09, Joshua Franklin wrote:

 
> > 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?
> > 
> > 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. 
> OK. I'll get this done today and to the list soon. The
> new game I just bought (Civ3) requires a better
> refresh rate than my old monitor can handle anyway.
> (Sniff)
> Just to make sure, I'm understanding this as:
> 1. "Required" (or "Base") is unquestionably installed
> packages (bash cygwin shellutils) that setup.exe needs

Base. I've trashed Required (it was a name holder from when I put the
dependency code together.)

> 2. "Core" is packages most people expect (man sed vim
> which) even though you can do useful things without
> them

No. For now lets simply identify the packages. There are a coupla ways
we can get them installed by the mad clicker.

> 3. Stuff people don't realize they need (groff
> ncurses) should *not* be in either one, since they'll
> get grabbed as dependencies anyway.

Yes.

Rob


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]