unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: [PATCH] doc: INSTALL: note OpenBSD xapian-bindings-perl package
Date: Thu, 24 Aug 2023 22:30:25 +0200	[thread overview]
Message-ID: <20230824223025+0200.280217-stepnem@smrk.net> (raw)
In-Reply-To: <20230824193509.3709766-1-e@80x24.org>

On Thu, 24 Aug 2023 19:35:09 +0000
Eric Wong wrote:

> The `xapian-bindings-perl' package contains the Xapian.pm
> SWIG bindings, but doesn't adhere to the existing convention
> of naming system packages after the Perl package name itself

I'm not familiar with the history of Xapian upstream or OpenBSD
packaging, but I'm guessing the main reason for the lack of "adherence"
here is that the package is being built together with the other language
bindings from the Xapian tarball (as opposed to, say, CPAN):

https://github.com/openbsd/ports/blob/master/databases/xapian-bindings/Makefile

Tangentially related: I've taken this opportunity to review my (OpenBSD)
install script and found one other package I needed to install that
isn't mentioned in INSTALL, namely, p5-IO-Socket-SSL.

I didn't report it or give it too much thought at the time, as I was
under the impression that the INSTALL file wasn't quite up-to-date or
definitive, anyway (that impression being corroborated by my previous
experience installing public-inbox on Arch Linux: IIRC there were some
dependency surprises there, too, unfortunately I didn't keep any notes
then), but seeing you touching these parts now I figured I'd mention it.

-- 
Štěpán

  reply	other threads:[~2023-08-24 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 19:35 [PATCH] doc: INSTALL: note OpenBSD xapian-bindings-perl package Eric Wong
2023-08-24 20:30 ` Štěpán Němec [this message]
2023-08-24 21:51   ` Eric Wong
2023-08-25 15:19     ` Štěpán Němec
2023-08-25 20:43       ` Eric Wong
2023-08-26  6:03         ` 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=20230824223025+0200.280217-stepnem@smrk.net \
    --to=stepnem@smrk.net \
    --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.
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).