From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: cygwin-pkg-maint enhancements
Date: Sun, 11 Jun 2023 19:01:08 +0100 [thread overview]
Message-ID: <8f7b29fc-83c5-0d77-994f-21e79542e3b9@dronecode.org.uk> (raw)
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.
This is all done in a single-pass parser at the moment, so group
definitions must precede packages which use them.
(Adding this was partially motivated by the fact that I've been
laboriously identifying and adopting packages which have X.Org as their
upstream, but there's no way to record that as a group of packages for
future reference)
next reply other threads:[~2023-06-11 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 18:01 Jon Turney [this message]
2023-06-16 9:47 ` Corinna Vinschen
2023-06-18 11:06 ` Jon Turney
2023-06-19 8:35 ` Corinna Vinschen
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=8f7b29fc-83c5-0d77-994f-21e79542e3b9@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).