This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Fixing packages which rely on obsolete packages

From: Ken Brown <kbrown at cornell dot edu>
To: cygwin-apps at cygwin dot com
Date: Sun, 23 Jun 2013 07:30:14 -0400
Subject: Re: Fixing packages which rely on obsolete packages
References: <20130622204921 dot GA2803 at ednor dot casa dot cgf dot cx> <20130622211341 dot GA3271 at ednor dot casa dot cgf dot cx> <51C6B865 dot 9070803 at users dot sourceforge dot net>

On 6/23/2013 4:57 AM, Yaakov (Cygwin/X) wrote:

On 2013-06-22 16:13, Christopher Faylor wrote:

Here's a similar list for 64-bit packages.  Apparently genini's error
checking leaves something to be desired.  Obviously some of these are
not obsolete.


Some of these actually are, meaning that they were copied straight from
their x86 version and not generated by cygport.

Another cause for such errors is that a .cygport file might have aREQUIRES line that refers to packages that haven't yet been added to the64-bit distro. I wonder if cygport should issue a warning if there is apackage listed in REQUIRES that is not installed on the user's system,just as it now does for DEPEND.

Ken

References:
- Fixing packages which rely on obsolete packages
  - From: Christopher Faylor
- Re: Fixing packages which rely on obsolete packages
  - From: Christopher Faylor
- Re: Fixing packages which rely on obsolete packages
  - From: Yaakov (Cygwin/X)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]