From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Fwd: calm: cygwin package report for Ken Brown
Date: Tue, 21 Mar 2023 09:55:21 +0100 [thread overview]
Message-ID: <ZBlw+Ve8JwRJ2Dyn@calimero.vinschen.de> (raw)
In-Reply-To: <732a2547-1815-9bfc-8727-b4a7790bb2c8@dronecode.org.uk>
On Mar 20 23:17, Jon Turney via Cygwin-apps wrote:
> On 20/03/2023 22:17, Ken Brown via Cygwin-apps wrote:
> > It looks like my plan for having scallywag deploy all the TeX Live
> > packages won't work (see below). calm would have to be more permissive
> > and allow deploying a package that requires something that will be
> > provided by a future package.
> >
> > In this case, I made asymptote require tl_2023, which will be provided
> > by the next texlive release. But I don't want to deploy the latter
> > until all the other packages for TeX Live 2023 have been deployed.
> >
> > Unless this is easy to fix, I'll just forget about using scallywag and
> > go back to my old method of uploading everything manually.
>
> This is trivially fixable.
>
> calm already has a list of 'provides which don't exist (yet)', so I think I
> just need to add tl_2023 and tl_basic_2023 to that list
>
> Future work: make these regexes so we don't have same problem again in a
> years time.
Wouldn't it make sense to be able to define this in the cygport file
somehow? Or does that open a can of worms?
Corinna
next prev parent reply other threads:[~2023-03-21 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167934943239.2863900.10205375643162783483@server2.sourceware.org>
2023-03-20 22:17 ` Ken Brown
2023-03-20 23:17 ` Jon Turney
2023-03-20 23:42 ` gs-cygwin.com
2023-03-21 2:10 ` Ken Brown
2023-03-21 8:55 ` Corinna Vinschen [this message]
2024-02-19 18:59 ` Ken Brown
2024-02-19 19:22 ` Jon Turney
[not found] <168313524287.291104.13797346226214774348@server2.sourceware.org>
2023-05-04 16:24 ` Ken Brown
2023-05-05 17:16 ` Jon Turney
2023-05-05 18:04 ` Brian Inglis
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=ZBlw+Ve8JwRJ2Dyn@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).