From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: Re: thoughts on Git::Raw / libgit2? Date: Thu, 25 Jun 2020 04:31:36 +0000 Message-ID: <20200625043136.GA1028@dcvr> (raw) In-Reply-To: <20200622192406.GF13113@chatter.i7.local> Konstantin Ryabitsev <email@example.com> 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 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 \ --firstname.lastname@example.org \ --email@example.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
user/dev discussion of public-inbox itself This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \ firstname.lastname@example.org public-inbox-index meta Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.io/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/public-inbox.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git