RE: [ANNOUNCEMENT] Server Test 22

[Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>]

 Alan

You can put cygz fix in CVS.  It is Ok.  We will use zlib from cygwin.

I raised a questiona  while ago about xpm that not not many applications use
xpm without a X, example was given XEmacs does.  I would say stick it with
your XEmacs port then to stick into cygwin with headers, while we know Xpm
was in XFree86... this is what I called forking and creating headache for
developers on this list, because then we dual heaers adn libraries on the
system and will be have questions about.
I see libfreetype and fonts libraries hanging around and I suspect they will
popup in contrib directory, perhaps some day, just like a year ago libz did
followed by xpm.  
There should be coordination and developers who are actively particapting in
cygwin development did mention the source or at least said they are same as
in Cygwin/XFree86... I classify it as forking of dll and creating a support
issues over here.

Cygipc is OK to use, but again properly it should names libipc.a, For many
applications when you run ./configure they look for libipc.a.  However, this
is a minor issue for our project.

We will mention in FAQ cygz.dll and Cygwip... my warning was about other
libraries which are already being used by Cygwin/XFree86, like libfreetype,
fonts, and xpm, start showing up in contrib I will rather take off then to
deal with issue.  If users need those libraries individually then we can
package them as separate libraries... 

Suhaib

-----Original Message-----
From: Alan Hourihane
To: cygwin-xfree@cygwin.com
Sent: 5/3/2001 8:12 PM
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 ?

Not everyone will use setup.exe.

> I also don't understand this talk about "forking".  Chuck has made a
> libz available from the original sources at info-zip.org.  This is by
> no means an XFree86 package.  It was developed by the author of gzip.
> It lives here:
> 
I don't understand the forking issue either.

> http://www.info-zip.org/pub/infozip/zlib/
> 
> Chuck provided a generic port of the package for use with Cygwin.
IMO,
> this is what this project should be using.
> 
I agree here. Any application should use operating system provided
libraries
rather than building it's own. That was the original reason for the
patch
to use cygwin's provided one. I only reversed it as the zlib for cygwin
was in contrib.

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.


A