Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B5B0109.70600@ece.gatech.edu>
Date: Sun, 22 Jul 2001 12:36:25 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: E <ecognito1 AT earthcorp DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Did some porting for cygwin
References: <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20010722165317 DOT 00a07610 AT bastion DOT datatask DOT com DOT au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

E wrote:

> At 10:46 PM 21/07/2001 -0400, Charles S. Wilson wrote:
> 
>> Marcus Börger wrote:
>>
>>> +freetype.2.0.4
>>
>>
>> NO.  this is included in the cygwin-xfree project.  We shouldn't have 
>> two different (conflicting?) versions of the same thing.
>>
>> --Chuck
> 
> 
> In that case, seeing as it appears to be useful for more than just X 
> applications, would it be worthwhile moving it from the cygwin-xfree 
> project to a package under the base cygwin distribution?


Actually, The Right Thing(tm) to do is:
   (a) wait for the dependency stuff in setup.exe to settle down.
   (b) which is a pre-req for: convince Suhaib/others to split up the 
xfree distribution into package-pieces.  Currently, *all* DLLs are in a 
monolithic tarball, even though fonts have their own tarball, the server 
has its own tarball, etc.  E.g. "freetype" binaries are intermingled 
with everything else; the packaging is not source-code-dist specific.
   (c) convince Suhaib/others to also add the freetype *exe's* to this 
(as-yet-nonexistent) freetype tarball (currently, only libs and headers 
are included in the monolithic "all-dlls" tarball.)
   (d) migrate all cygwin-xfree packages over to the "official" 
distribution/setup.exe structure.

AFAIK, this ^^^^ is the current plan of action for cygwin-xfree (well, 
(a) and (d) are; (b) & (c) are my wish-list for freetype).


> Still only one version, but a wider audience.  Freetype compiled with no 
> actual source modifications once you'd frigged around with one of the 
> config files a bit IIRC, so unless there are some cygwin-xfree patches 
> to it that make is unusable otherwise, it shouldn't be too difficult.


The cygwin-xfree people get justifiably upset when a "fork" like this 
happens (and make no mistake, what you're proposing is a fork -- or will 
become one once the inevitable version-skew happens).  Go read up on the 
xpm/xpm-nox "discussions" on the cgywin-apps and cygwin-xfree mailing lists.

Besides, freetype is useless without the X libraries, anyway.  If they 
are going to do the work, let them.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/