On 10/04/2025 11:29, Philippe Baril Lecavalier via Cygwin-apps wrote:
On Tue, Apr 8, 2025 at 3:48 PM Jon Turney
<jon.turney-grjqepx9rppnlxjtenl...@public.gmane.org.uk> wrote:
In future, if you could please attach patches to emails, that makes them
easier to use.
Of course. When in doubt, I follow LKML's long established practice.
Good to know mime type attachments supported here!
A few questions that came up along the way:
1. Do you sign git commits (-S, --gpg-sign) or advise to do so?
There is no policy, currently.
So, you can sign commits if you like.
2. This package has no reverse dependencies, is not too complicated,
so I guess it's a case for straight to "stable" without the need for
testing probation period. What are the criteria for a package to be
deployed initially as "test"? I'm guessing
compilers/interpreters/toolchain/anything heavily patched.
The use of 'test' (unstable) status is at the package maintainer's
discretion.
Unfortunately, unless you make a special pleading to the userbase, your
test package is unlikely to seem much use, so it's not really a very
useful status.
Generally, I wouldn't suggest using it unless you have legitimate
worries that the package might not work properly.
Yes, this could all be done so much better :(
3. Treecleaning. There were 3 older versions of the package nano
present. Is it the responsibility of the maintainer to tidy up? (If
so, how?) Unless there is a business case for older versions, and if
no hate mail arrived some time after the latest update (weeks,
months), I guess it's safe to purge.
A question has arisen, which you have hopefully already seen:
https://cygwin.com/pipermail/cygwin/2025-April/257918.html
- Actually, I see that
https://cygwin.com/package-upload.html#deleting seems to handle some
of that. I see it took out the oldest, 2.9.7 (`calm` emailed me so),
but 4.3 and 4.9 remain there for now.
Yeah, this probably needs to be touched upon in the "Contributor's
Guide", but in general, you shouldn't need to do anything.
By default, a total of three versions are retained in the package
repository, and low versions are removed to keep under that limit.
(But you can configure the policy and manually remove versions if you
need to, as indicated there)
4. Is there an easy way to download the whole tree of *.cygport files?
I'm only looking for a snapshot of the files if possible, not the
totality of git repos. That would help to "check/consult/figure out
something", instead of using web browser, very slowly.
No, this doesn't exist. Sorry.
But we really don't mind people making git clones, so if you want to get
a load of cygport files to grep through and whatnot, this is relatively
easy to script:
* fetch the list of packages from https://cygwin.com/cygwin-pkg-maint
* ignore lines starting with '#' or '@;
* the first white-space separated token on each line is the package name
* git clone git://cygwin.com/git/cygwin-packages/<packagename>
(ignore errors as this won't exist for some old packages)
* probably put a small delay before moving on to the next line
Season to taste with '--depth=1' and error handling.
I actually have a script like that somewhere, but can't find it right now :(
