This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: [ANNOUNCEMENT] Server Test 22
- To: "Alan Hourihane" <alanh at fairlite dot demon dot co dot uk>,<cygwin-xfree at cygwin dot com>
- Subject: RE: [ANNOUNCEMENT] Server Test 22
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Fri, 4 May 2001 12:43:33 +1000
> -----Original Message-----
> From: Alan Hourihane [mailto:alanh@fairlite.demon.co.uk]
> Sent: Friday, May 04, 2001 10:13 AM
> To: cygwin-xfree@cygwin.com
> Subject: Re: [ANNOUNCEMENT] Server Test 22
>
>
> On Thu, May 03, 2001 at 05:55:19PM -0400, Christopher Faylor wrote:
> > On Fri, May 04, 2001 at 07:40:21AM +1000, Robert Collins wrote:
> > >Just a lemma: end users are advised to use setup.exe to
> install cygwin.
> > >
> > >They do __not__ see contrib vs latest.
> >
> > Right. Good point! This whole contrib argument is really
> a non-issue
> > in this light.
> >
> What's the point in having contrib then if it doesn't mean anything ?
It used to. It still can via flags in the setup.hint file.. but I don't
believe there is a visual warning to anything.
> Not everyone will use setup.exe.
They have no other option. untarring doesn't create the registry entries
and run the install scripts. winzip doesn't create symlinks.
>
> In light of cygipc too, which is really in contrib land, I suggest we
> put it back. Especially being that the next XFree86 release
> is due very soon and
> many more users will probably download the new Cygwin/XFree86. We have
> a chance to correct the zlib situation.
>
> It's a one off thing. Let's get it right now and suffer a few
> emails (and
> put it in the FAQ), that people need to get the zlib from
> contrib to use
> Cygwin/XFree86. We probably stand to get more questions on
> which cygz.dll or
> libz.dll they should be using otherwise.
>
> Are we expecting to build the next full release with cygipc ?
> If so, then
> that should be made aware in the FAQ too.
I wouldn't! IMO it would be better to hold off until ipc is part of
cygwin core. (I.e. threads could have been done way back via the
win32-pthread project but fork() would have been an issue. (And may be
with cygipc for all I know).
Rob
>
> A
>