From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: Re: thoughts on Git::Raw / libgit2?
Date: Thu, 25 Jun 2020 04:31:36 +0000 [thread overview]
Message-ID: <20200625043136.GA1028@dcvr> (raw)
In-Reply-To: <20200622192406.GF13113@chatter.i7.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Jun 16, 2020 at 09:40:51PM +0000, Eric Wong wrote:
> > Git::Raw is not packaged with CentOS 7.x; but cpan/cpanm is an
> > option. It is in Debian 10.x as libgit-raw-perl, so I can
> > report bugs via Debian's BTS[*].
>
> FYI, even though lore.kernel.org runs on CentOS 7.x, most perl modules
> come from cpan -- so if your reluctance to use it is based on lore
> usage, that's not something we'd be particularly concerned about.
Thanks for the response. lore is definitely a big factor of
consideration, but I would also like to make it easier for
others to mirror lore w/o needing CPAN.
Fwiw, CentOS 7.x does have libgit2-devel and Inline::C packaged;
so that's an option, too.
Given the announcement of Perl 7 today makes me a little
uneasy(*), I might be a bit more inclined to introduce more
functionality via Inline::C.
(*) Perl 7 will probably be less painful than the Python 3 or
Ruby 1.9 transitions, but those are low bars. Having "only"
a ~decade-long support window for old Perl 5 stuff doesn't
seem sufficient. I guess distros and users (myself included)
will need to do our part to keep things from breaking and
possibly extend maintenance indefinitely.
next prev parent reply other threads:[~2020-06-25 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 21:40 thoughts on Git::Raw / libgit2? Eric Wong
2020-06-22 19:24 ` Konstantin Ryabitsev
2020-06-25 4:31 ` Eric Wong [this message]
2020-09-19 9:50 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200625043136.GA1028@dcvr \
--to=e@yhbt.net \
--cc=meta@public-inbox.org \
/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).