From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Using lei with podman + toolbox
Date: Fri, 10 Sep 2021 13:56:53 +0000 [thread overview]
Message-ID: <20210910135653.GA22719@dcvr> (raw)
In-Reply-To: <20210910124242.rwjujckpd4arupr2@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Thu, Sep 09, 2021 at 11:36:14PM +0000, Eric Wong wrote:
> > > These are my quickie instructions for how to use lei in a toolbox environment
> > > if you are running a distribution like Fedora and don't want to install a lot
> > > of perl dependencies into your main OS.
> >
> > Off the top of my head, I think Search::Xapian // Xapian.pm was
> > the main thing that was missing from CentOS 7. Does Fedora have
> > that?
>
> Seems to have it as perl-Search-Xapian, which provides Xapian.pm.
Oh I meant the newer SWIG Xapian.pm. Search::Xapian is
Search/Xapian.pm which uses XS and isn't getting new features.
The XS version is far better-tested, but the SWIG version gives
access to some newer APIs. AFAIK neither lets us do custom
query parsing like notmuch does in C++ (our approxidate
rt:/dt:/d: handling is a huge hack)
> > (disclaimer: I don't care for Docker, seems like a giant waste
> > of space and bandwidth compared to just using the distro)
>
> Well, this is for toolbox which uses podman, not docker. Toolbox is actually
> the preferred mechanism in Fedora for setting up quickie work environments,
> especially on something like Fedora Silverblue with its immutable root
> partition.
Ah, still seems like a waste of space and bandwidth :>
(It just took me several hours to download upgrades from
buster => bullseye on a small dev VM)
> I don't intend these instructions as the preferred mechanism for getting lei
> up and running, just to be clear. Eventually, it will be packaged for most
> distros -- but for now it's a convenient way to get the latest version on the
> platform most likely to be most tested (Debian).
I actually test everything on FreeBSD to force myself into doing
things portably. Probably 95% of my "git push" is done on
FreeBSD (IOW, whenever I have connectivity to that VM).
> All noted -- I may be the one who packages things for Fedora at some point, so
> this is useful info.
Cool. I'm wondering how to better arrange INSTALL to suit
different usages (lei-only vs daemons vs mda/watch-only).
next prev parent reply other threads:[~2021-09-10 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 21:39 Using lei with podman + toolbox Konstantin Ryabitsev
2021-09-09 23:36 ` Eric Wong
2021-09-09 23:51 ` native C++ Xapian wrapper [was: Using lei with podman + toolbox] Eric Wong
2021-09-10 12:42 ` Using lei with podman + toolbox Konstantin Ryabitsev
2021-09-10 13:56 ` Eric Wong [this message]
2021-09-10 14:48 ` Konstantin Ryabitsev
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=20210910135653.GA22719@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.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.
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).