user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: newer xapian and git packages for CentOS7
Date: Fri, 23 Apr 2021 15:51:01 -0400	[thread overview]
Message-ID: <20210423195101.esyddcxcauhzzwuo@nitro.local> (raw)
In-Reply-To: <20210423191849.GA23753@dcvr>

On Fri, Apr 23, 2021 at 07:18:49PM +0000, Eric Wong wrote:
> > > Btw, I noticed xapian14-bindings isn't packaged.  If it were, it
> > > would include the better-maintained Xapian.pm (SWIG) binding.
> > > Getting Search::Xapian (XS) from CPAN would no longer be
> > > necessary.
> > 
> > Hmm... I mostly haven't because cross-package dependencies with copr is a bit
> > hairy (and looking at the SPEC file, I'm not sure it will work with the
> > ancient Ruby package in EL7). I'll give it a try, but if there is no great
> > benefit of using Xapian.pm as opposed to Search::Xapian, then I may not try
> > too hard. :)
> 
> Ah, no worries.  public-inbox isn't currently using features
> exclusive to Xapian.pm, but may start doing so for query parser
> customizations (or just-ahead-of-time C++).  Search::Xapian
> remains the only option within Debian packages, atm...

It was actually less hairy than I'd anticipated. I build
xapian14-bindings-perl and it seems to work find as a drop-in replacement for
Search::Xapian. The package is in the same copr repository as xapian14-core.

Thanks for the suggestion.

-K

      reply	other threads:[~2021-04-23 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 15:13 newer xapian and git packages for CentOS7 Konstantin Ryabitsev
2021-04-23  6:02 ` Eric Wong
2021-04-23 19:12   ` Konstantin Ryabitsev
2021-04-23 19:18     ` Eric Wong
2021-04-23 19:51       ` Konstantin Ryabitsev [this message]

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=20210423195101.esyddcxcauhzzwuo@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).