From: Daisuke Fujimura <booleanlabel@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] gflags 2.2.2
Date: Mon, 4 Dec 2023 20:01:55 +0900 [thread overview]
Message-ID: <CAA3frXR45-cKhU27OcnF98uA6XzZ1bj0qK-KE585Ev1dX6kmvQ@mail.gmail.com> (raw)
In-Reply-To: <80cc2424-2550-4742-9afe-40128c892c7f@dronecode.org.uk>
Thank you for your review.
I will merge the documentation and scripts into the runtime package.
gflags.cygport diff :
https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=3d92ec96da0cfb58ffee465eb65eec2f0b923f19
CI : https://github.com/cygwin/scallywag/actions/runs/7085452227
On Mon, Dec 4, 2023 at 12:06 AM Jon Turney <jon.turney@dronecode.org.uk> wrote:
>
> On 25/11/2023 08:55, Daisuke Fujimura via Cygwin-apps wrote:
> >> The one question I have is about what 'gflags_completions.sh' is for? Is
> >> this a helper for scripts other packages using gflags might install in
> >> /etc/bash_completion.d/, or an example? or generally useful?
> >
> > gflags_completions.sh is a script that generates completions for
> > options supported by gflags.
> >
> > - https://stackoverflow.com/questions/32555861/how-to-get-bash-tab-completions-for-your-own-project-with-gflags
> >
> > Also, since major distributions such as arch and fedora include this
> > script in their packages, we decided it would be better to include it
> > in the cygwin package as well.
> >
> > - https://archlinux.org/packages/extra/x86_64/gflags/files/
> > - https://src.fedoraproject.org/rpms/gflags/blob/rawhide/f/gflags.spec
> >
> > However, perhaps this should be included in runtime or development.
>
> Thanks. That makes perfect sense.
>
> Yeah, it seems like perhaps it should be with the runtime, I think.
>
next prev parent reply other threads:[~2023-12-04 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 23:20 Daisuke Fujimura
2023-11-20 17:13 ` Jon Turney
2023-11-25 8:55 ` Daisuke Fujimura
2023-12-03 15:06 ` Jon Turney
2023-12-04 11:01 ` Daisuke Fujimura [this message]
2023-12-05 13:04 ` Jon Turney
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=CAA3frXR45-cKhU27OcnF98uA6XzZ1bj0qK-KE585Ev1dX6kmvQ@mail.gmail.com \
--to=booleanlabel@gmail.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).