From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] gengetopt 2.23
Date: Mon, 30 Nov 2020 14:46:53 -0500 [thread overview]
Message-ID: <d4bd91f2-6ada-b300-f429-a12199c07348@cornell.edu> (raw)
In-Reply-To: <8842c6fe-3a5d-5d5f-5691-2d756ee89174@upc.edu>
On 11/29/2020 2:19 PM, Rafel Amer Ramon wrote:
>
> Hi,
>
> [ITP] gengetopt 2.23
>
> Program home page: https://www.gnu.org/software/gengetopt
>
> License: This program is free software; you can redistribute it and/or modify
> it under the terms of the GNU General Public License as published by
> the Free Software Foundation; either version 3 of the License, or
> (at your option) any later version.
>
> Debian package: https://packages.debian.org/buster/gengetopt
>
> I have uploaded the files to https://github.com/rafelamer/cygwin-gengetopt
>
> https://github.com/rafelamer/cygwin-gengetopt/raw/main/gengetopt.cygport
> https://github.com/rafelamer/cygwin-gengetopt/raw/main/gengetopt-2.23.tar.xz
>
>
> https://github.com/rafelamer/cygwin-gengetopt/raw/main/gengetopt-2.23-1.x86_64/dist/gengetopt/gengetopt-2.23-1-src.hint
>
> https://github.com/rafelamer/cygwin-gengetopt/raw/main/gengetopt-2.23-1.x86_64/dist/gengetopt/gengetopt-2.23-1-src.tar.xz
>
> https://github.com/rafelamer/cygwin-gengetopt/raw/main/gengetopt-2.23-1.x86_64/dist/gengetopt/gengetopt-2.23-1.hint
>
> https://github.com/rafelamer/cygwin-gengetopt/raw/main/gengetopt-2.23-1.x86_64/dist/gengetopt/gengetopt-2.23-1.tar.xz
This looks good. I just have a few minor comments.
- The SUMMARY should generally not start by repeating the package name. "A tool
to write command line option parsing code for C programs" suffices.
- I suggest adding
HOMEPAGE="https://www.gnu.org/software/gengetopt/"
- The build produces a source patch because of changes to test files:
>>> Creating source patches
tests/test_conf_parser_ov2.c | 2 +-
tests/test_conf_parser_ov3.c | 4 ++--
tests/test_conf_parser_ov4.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
You can use DIFF_EXCLUDES to avoid this.
- There are two failing tests that you might want to look into at some point.
- I noticed that your github repo contains all the build files. Once you become
maintainer, you will be able to push to the official source repo for the package
(see https://cygwin.com/packaging/repos.html). This should not contain only the
files needed for building the package (i.e., only the cygport file in your
case). Pushing to that repo triggers an automatic build (see
https://cygwin.com/cgi-bin2/jobs.cgi).
I'll go ahead and add you to https://cygwin.com/cygwin-pkg-maint, but I'm not
sure how to parse your name. Should it be "Rafel Amer" or "Rafel Amer Ramon" or
something else?
Thanks for becoming a maintainer.
Ken
next prev parent reply other threads:[~2020-11-30 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 19:19 Rafel Amer Ramon
2020-11-30 19:46 ` Ken Brown [this message]
2020-11-30 20:28 ` Ken Brown
2020-12-01 16:04 ` Rafel Amer Ramon
2020-12-01 17:23 ` Ken Brown
[not found] ` <c69ce275-f73e-8cb8-1e5f-05bc5d0bfdfc@upc.edu>
2021-02-25 18:39 ` Ken Brown
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=d4bd91f2-6ada-b300-f429-a12199c07348@cornell.edu \
--to=kbrown@cornell.edu \
--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).