public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Fwd: calm: cygwin package report for Ken Brown
Date: Mon, 20 Mar 2023 22:10:00 -0400	[thread overview]
Message-ID: <8be3ed98-e591-f07a-45db-e00ed282f28c@cornell.edu> (raw)
In-Reply-To: <732a2547-1815-9bfc-8727-b4a7790bb2c8@dronecode.org.uk>

On 3/20/2023 7:17 PM, Jon Turney 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.

[...]

> 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

Thanks!

[...]

> Maybe calm doesn't need to do this kind of check any more?
> 
> But then people might write REQUIRES="typoed-package-name" and not 
> notice until it's uninstallable, so I don't know.

I don't know either, but I think I lean toward not doing the check, in 
order to give maintainers maximum flexibility.  In your example, the 
problem is easily fixed as soon as the maintainer (or someone else) 
notices that the package is uninstallable.  And when they try to select 
it for installation, setup will immediately tell them what the problem is.

Ken

  parent reply	other threads:[~2023-03-21  2:10 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 [this message]
2023-03-21  8:55     ` Corinna Vinschen
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=8be3ed98-e591-f07a-45db-e00ed282f28c@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).