From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Achim Gratz <Stromeko@nexgo.de>
Subject: Re: cygport
Date: Sun, 10 Apr 2022 19:44:54 +0100 [thread overview]
Message-ID: <269eb1ed-452c-5aa5-eb33-8b8ded108a1c@dronecode.org.uk> (raw)
In-Reply-To: <87ee2nttqt.fsf@Rainer.invalid>
On 27/03/2022 14:22, Achim Gratz wrote:
> Jon Turney writes:
>> A few comments after looking at:
>>
>> lib/pkg_info.cygport: implement automatic determination of the
>> appropriate perl5_0xy requirement
>> 1. In __list_deps(), this should look at the files list in $@, not at
>> files in $D, as that causes it to identify a perl5_0xy dependency for
>> all subpackages, irrespective of which package (if any) contains the
>> files in the vendor_perl directory.
>>
>> 2. This only identifies the perl5_0xy requirement for packages which
>> own files in the vendor_perl directory, not for packages which contain
>> executables or shared libraries dynamically linked with
>> cygperl5_xy.dll. That should at least be mentioned in the patch
>> commentary.
>
> I've fixed both of these on the to-upstream branch I think.
Thanks.
I tried testing this on rxvt-unicode. It correctly adds the perl5_032
dependency due to linkage
But it also emits a bogus dependency on 'Carp'.
> @@ -412,6 +413,7 @@ __list_deps() {
> do
> if [ -f ${d}/${pldep//:://}.pm ]
> then
> + case "${d##*/}" in 5.[0-9][0-9]) plver+="$pldep " ;; esac
Is the mistake thinking pldep here is a pathname, not a module name?
> alldeps+=" "${d}/${pldep//:://}.pm;
> break;
> fi
> @@ -419,6 +421,17 @@ __list_deps() {
> done
> fi
>
> + plver=( $( echo "${plver}" | tr ' ' '\n' | sed -e 's/.*\///;s/5/perl5/;s/\./_0/' | sort -ru ) )
> + if [ "${#plver[@]}" -gt 1 ]
> + then
> + warning "More than one targeted Perl version: ${plver[*]},"
> + warning "using only the latest as dependency: ${plver[0]}."
> + fi
> + if [ "${#plver[@]}" -gt 0 ] && [ "${PN}" != "perl_base" ]
> + then
> + echo "${plver[0]}"
> + fi
> +
> if check_prog php-config
> then
> phpmoddir=$(php-config --extension-dir)
next prev parent reply other threads:[~2022-04-10 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:10 cygport Achim Gratz
2022-03-14 19:06 ` cygport Jon Turney
2022-03-14 20:12 ` cygport Achim Gratz
2022-03-14 20:50 ` cygport Jon Turney
2022-03-27 13:22 ` cygport Achim Gratz
2022-04-10 18:44 ` Jon Turney [this message]
2022-04-10 18:57 ` cygport Achim Gratz
2022-09-15 17:45 ` cygport Jon Turney
2022-09-15 19:34 ` cygport 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=269eb1ed-452c-5aa5-eb33-8b8ded108a1c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Stromeko@nexgo.de \
--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).