From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: thoughts on Git::Raw / libgit2?
Date: Tue, 16 Jun 2020 21:40:51 +0000 [thread overview]
Message-ID: <20200616214050.GA15110@dcvr> (raw)
Hey all,
First off, I have no intention of making Git::Raw (Perl libgit2
wrapper) or libgit2 a hard dependency. It'll be an option if
available, like most of our dependencies.
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[*].
I only intend to use Git::Raw for blob retrievals as a separate
AF_UNIX SOCK_STREAM daemon similar to how we use
`git cat-file --batch/--batch-check'.
The socket/pipe interface works well for unpredictable seek
times on HDDs. Using Git::Raw from an AF_UNIX SOCK_STREAM
daemon would allow us to save pipe buffers, and PIDs when
there's tens/hundreds of thousands of git repos involved.
[*] I have no intention of ever using a proprietary service for
free software development. Even if GitHub were free software,
their terms-of-service is unacceptable to me.
next reply other threads:[~2020-06-16 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 21:40 Eric Wong [this message]
2020-06-22 19:24 ` thoughts on Git::Raw / libgit2? Konstantin Ryabitsev
2020-06-25 4:31 ` Eric Wong
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=20200616214050.GA15110@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).