From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Scallywag glitch with texlive-collection-* packages
Date: Mon, 14 Sep 2020 14:11:34 -0600 [thread overview]
Message-ID: <99211ca4-a9be-ca3e-6c42-8012de05e1c5@SystematicSw.ab.ca> (raw)
In-Reply-To: <dfb7da6f-a59c-871c-d6a3-4d41ea6fc7d9@dronecode.org.uk>
On 2020-09-14 05:47, Jon Turney wrote:
> On 13/09/2020 23:48, Ken Brown via Cygwin-apps wrote:
>> Jon,
>>
>> All texlive-collection-* packages are noarch. This is defined in
>> texlive.cygclass, so scallywag doesn't see it. I just let scallywag
> Yeah, this is an unfortunate consequence of trying to guess this stuff by
> looking at the .cygport, rather than running (some yet to be written mode of)
> cygport to process it and output the needed information.
>
> I've made scallywag aware that 'inherit texlive' implies noarchness, so it
> should get it right going forward.
Any changes made or needed in cygport or scallywag for mingw64 packages?
I've rebuilt and reuploaded both Mingw curl noarches to see if they make it.
I found that for cygport NAME must be a hardcoded constant string not requiring
script evaluation; hopefully other content is evaluated in the script context
and does not also require to be hardcoded constants.
--
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 IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-09-14 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 22:48 Ken Brown
2020-09-14 11:47 ` Jon Turney
2020-09-14 20:11 ` Brian Inglis [this message]
2020-09-15 5:34 ` ASSI
2020-09-16 5:13 ` Brian Inglis
2020-09-16 13:54 ` Brian Inglis
2020-09-20 19:18 ` Jon Turney
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=99211ca4-a9be-ca3e-6c42-8012de05e1c5@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).