This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Sample setup.ini
- To: cygwin-developers at cygwin dot com, Christopher Faylor <cgf at redhat dot com>, cygwin-developers at sources dot redhat dot com
- Subject: Re: Sample setup.ini
- From: Brian Keener <bkeener at thesoftwaresource dot com>
- Date: Mon, 02 Jul 2001 12:54:11 EDT
- References: <000201c1014a$19cf53b0$6464648a@ca.boeing.com> <04c901c10160$4005e1a0$806410ac@local> <20010630120243.D12695@redhat.com> <20010630153329.A16134@redhat.com>
- Reply-To: bkeener at thesoftwaresource dot com
Christopher Faylor wrote:
> If you check out the pre_category branch, you'll get a version of setup.exe
> before Robert's category changes. The way I usually do this is:
>
> cd winsup
> rsync -a cinstall/ precinstall
> cd precinstall
> cvs update -rpre_category
>
Michael Chase wrote:
> The precinstall version doesn't have the rule necessary to accept multiple
> categories for a package. I think that is one of the desired features the
> upcoming version will provide.
Okay,
I'm confused now (playing catchup again). So people like me can keep up with
this we now have two branches of cvs for cinstall - right? Chris' message
seems to imply that precinstall is the version of setup that would be most like
what we would get from the web page as an average user - without any of the new
stuff but then Michael' message seems to imply that the new stuff is broken in
the precinstall version.
Which is it or where did my interpretation go goofy. Is it the
*Pre*vious*Cinstall* or the *Pre*liminary*Cinstall*?
bk