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: [PATCH setup] Report dependencies which don't exist


On Jul  7 16:36, Jon Turney wrote:
> On 07/07/2016 15:59, Corinna Vinschen wrote:
> > On Jul  7 14:46, Jon Turney wrote:
> > > At the moment, dependencies which can't be found are silently ignored.
> > > Instead, record and report these dependency problems.
> > 
> > Nice idea.
> > 
> > One question, though.  Apart from getting a report which won't be read,
> > what is a user supposed to do?
> > 
> > In theory, shouldn't calm make sure that the deps exist?
> 
> Yes, in fact it already does so.
> 
> However, that doesn't help in the case of cross-repo dependencies (e.g
> cygwinports contains several packages which depend on cygwin packages which
> seem to have been removed or renamed)
> 
> It would be nice to have a tool to detect those problems at setup.ini
> generation time, but that doesn't exist yet.
> 
> Additionally, adding this check reveals a problem with the way this check is
> done in calm, as it reports the following as non-existent dependencies:
> 
> gcc4 (x86 only) -> gcc
> logiweb (x86 only) -> gcc
> varnish -> gcc, libedit
> 
> This is because setup has, by this stage, discarded source-only packages,
> which it doesn't make any sense to depend on.
> 
> I'll make calm check for odd dependencies like that, once I've fixed those
> on sourceware.

Thank you.  Please feel free to apply the patch.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: signature.asc
Description: PGP signature


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