public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygwin-pkg-maint enhancements
Date: Mon, 19 Jun 2023 10:35:34 +0200	[thread overview]
Message-ID: <ZJATVuU68mZrT0kV@calimero.vinschen.de> (raw)
In-Reply-To: <d51dcaa9-947c-7aaa-b16f-c63cc4037d35@dronecode.org.uk>

On Jun 18 12:06, Jon Turney via Cygwin-apps wrote:
> On 16/06/2023 10:47, Corinna Vinschen via Cygwin-apps wrote:
> > On Jun 11 19:01, Jon Turney via Cygwin-apps wrote:
> > > 
> > > I've deployed an update to calm which makes a few small improvements to the
> > > way cygwin-pkg-maint is handled:
> > > 
> > > * Lines starting with a '#' are now ignored as a comment
> > > 
> > > * There's now a simple facility for grouping packages:
> > > 
> > > Define a group with a line starting with '@', e.g.:
> > > 
> > >      @upstream_project Maintainer1/Maintainer2
> > > 
> > > Then @upstream_project can used in a package's maintainer list, as a
> > > reference to that list of maintainers.
> > 
> > That's a great change. Thanks!
> > 
> > Would adding glob patterns help, too?  Kind of like
> > 
> >    aspell
> >    aspell-*
> > 
> 
> Well, maybe.
> 
> That's a more complex change, as the code just does a simple lookup by
> source package name at the moment.

Yeah, ok.  It would have to call the python glob function instead.
Assuming there is one, but I guess there is.

> It would also introduce the possibility for ambiguity. e.g. What is the
> following intended to mean?
> 
> aspell-*         Aye Person
> aspell-gibberish Anne Other

True. I thought we could simply avoid that, given we maintain the file
manually anyway.

Assuming the file is searched lineary from top to bottom, the problem
could be simply fixed by switching the order:

  aspell-gibberish Anne Other
  aspell-*         Aye Person

So, ordering from strict to fuzzy.

Anyway, it was just an idea.  We made it to here without globbing,
so it's not as if that would be necessary.


Corinna

      reply	other threads:[~2023-06-19  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 18:01 Jon Turney
2023-06-16  9:47 ` Corinna Vinschen
2023-06-18 11:06   ` Jon Turney
2023-06-19  8:35     ` Corinna Vinschen [this message]

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=ZJATVuU68mZrT0kV@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).