public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: scallywag cygport fails to detect perl script runtime dependencies
Date: Sat, 12 Mar 2022 09:49:54 -0700	[thread overview]
Message-ID: <167781b1-95ea-fb3e-ca67-18afd0b33df4@SystematicSw.ab.ca> (raw)
In-Reply-To: <62d41c03-9494-218a-4f64-fb7c27fa43b4@dronecode.org.uk>

On 2022-03-12 05:56, Jon Turney wrote:
> On 11/03/2022 17:50, Brian Inglis wrote:
>> Does cygport require perl modules to be installed as build 
>> dependencies in order to enable their detection as runtime 
>> dependencies for perl scripts in packages?

> Yes.
> See __list_deps in pkg_info.cygpart

Saw that under 'check_prog\sperl'.

> I don't know how we could traverse from module to package otherwise 
> (other interpreted languages e.g. python, etc., generally have the same 
> issue).

So we need to do this for all interpreted language scripts with language 
module dependencies supported in cygport.

> I don't see this a huge problem, as these dependencies would probably 
> need to be installed to run tests, if the package has any.

True: good point; ta!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-03-12 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 17:50 Brian Inglis
2022-03-12 12:56 ` Jon Turney
2022-03-12 16:49   ` Brian Inglis [this message]
2022-03-12 16:23 ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=167781b1-95ea-fb3e-ca67-18afd0b33df4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).