From: Felipe Contreras <email@example.com>
To: Jeff King <firstname.lastname@example.org>,
"brian m. carlson" <email@example.com>
Cc: Siavash <firstname.lastname@example.org>, email@example.com
Subject: Re: [Bug] git-credential-netrc.perl is not built and is not available in `exec-path`
Date: Sun, 23 May 2021 22:01:21 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Jeff King wrote:
> I suspect that just opening a bug report against distro packages might
> get some traction (especially if it comes with a patch to create the
> extra package).
I have tried that; do doesn't work. If git developers have $x in
"contrib" it's for a reason.
> I do wonder if packagers are hesitant to reach into
Of course they are! The word "contrib" has an obvious meaning.
This is precisely the reason why I tried to graduate "contrib/completion"
out of "contrib" to no avail .
If you want to install anything from "contrib" by default, it should be
"contrib/completion" first, which is already very well tested, and
shipped by many distributions. I would move it outside "contrib", to be
Then maybe "contrib/credential", sure, following "contrib/completion".
But to do a mish-mash between "/" and "/contrib". Does not make sense.
You can't eat your cake and have it too.
Either they are contributed, or they aren't.
>  I was actually surprised I had libsecret installed at all.
> Apparently pinentry-gtk2 links against it, which I have for use with
> gpg. But my system might not be considered typical anyway, as I
> don't use any kind of "desktop environment".
Unless you have a backend (like gnome-keyring) libsecret is useless.
Can you do "secret-tool lookup *" and fetch any of your passwords?
next prev parent reply other threads:[~2021-05-24 3:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 9:51 [Bug] git-credential-netrc.perl is not built and is not available in `exec-path` Siavash
2021-05-20 20:41 ` Jonathan Nieder
2021-05-21 10:26 ` Siavash
2021-05-21 1:55 ` brian m. carlson
2021-05-21 10:04 ` Jeff King
2021-05-21 22:27 ` brian m. carlson
2021-05-23 19:57 ` Jeff King
2021-05-24 3:01 ` Felipe Contreras [this message]
2021-05-24 10:05 ` Renaming "non-contrib" things out of contrib/* (was "Re: [Bug] git-credential-netrc.perl[...]") Ævar Arnfjörð Bjarmason
2021-05-24 17:21 ` Felipe Contreras
2021-05-24 23:18 ` Ævar Arnfjörð Bjarmason
2021-05-25 1:23 ` Felipe Contreras
2021-05-25 6:51 ` Junio C Hamano
2021-05-25 7:31 ` Bagas Sanjaya
2021-05-25 9:05 ` Felipe Contreras
2021-05-25 10:35 ` Felipe Contreras
2021-05-21 10:06 ` [Bug] git-credential-netrc.perl is not built and is not available in `exec-path` Jeff King
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).