From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Scallywag glitch with texlive-collection-* packages
Date: Tue, 15 Sep 2020 07:34:06 +0200 [thread overview]
Message-ID: <87363jhacx.fsf@Otto.invalid> (raw)
In-Reply-To: <99211ca4-a9be-ca3e-6c42-8012de05e1c5@SystematicSw.ab.ca> (Brian Inglis's message of "Mon, 14 Sep 2020 14:11:34 -0600")
Brian Inglis writes:
> 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.
If you're just trying out things push to the playground branch and
iterate it there until it works. You can force-push to this branch and
delete it afterwards if you want.
You still haven't added the necessary BUILD_REQUIRES correctly. Btw,
ZStandard is available both natively and for mingw64 in Cygwin.
> 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.
You need to lose that $XARCH monkey business as well. Scallywag just
looks at the file, it doesn't evaluate anything.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2020-09-15 5:34 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
2020-09-15 5:34 ` ASSI [this message]
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=87363jhacx.fsf@Otto.invalid \
--to=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).