Ken Brown kbrown@cornell.edu
Thu Jul 25 21:33:00 GMT 2013

On 7/25/2013 3:50 PM, Warren Young wrote:
> On 7/25/2013 02:30, Corinna Vinschen wrote:
>> On Jul 24 14:38, Warren Young wrote:
>>> On 7/24/2013 05:41, Corinna Vinschen wrote:
>>>> On Jul 24 05:12, Warren Young wrote:
>>>>> You'd have to fake a -3 package set, with libexpat-devel-3 set to
>>>>> obsolete libexpat1-devel-2, so that package developers would
>>>>> automatically get new packages on their next Cygwin update.
>>>> If you're willing to do that for 32 and 64 bit, ok.
>>> ...aren't I going to get exactly the same output tarballs as
>>> before, just with different names?
>> The content of the src packages won't match the new version if we
>> just copy the files.  A rebuild is simplest and cleanest.
> Okay.
> I'll wait for this PKG_OBSOLETES feature to ship in Cygport, and be a
> guinea pig for it.

While you're waiting, could you provide a setup.hint for libexpat1-devel 
(64 bit)?  Without a setup.hint, it gets put into the Misc category and 
is then installed by default.


More information about the Cygwin-apps mailing list