#1037176 ITP: typesense -- Fast, typo-tolerant search engine

Package:
wnpp
Source:
wnpp
Submitter:
Didier 'OdyX' Raboud
Date:
2025-12-26 19:03:23 UTC
Severity:
normal
#1037176#5
Date:
2023-06-07 05:56:21 UTC
From:
To:
  Package name    : typesense
  Version         : 0.24.1
  Upstream Contact: TypeSense team <contact@typesense.org>
  URL             : https://typesense.org
  License         : GPL-3
  Programming Lang: C++

Typo-tolerant search engine optimized for instant search-as-you-type
experiences and developer productivity. Push data to it and then allow
users to search through this data via a search UI in a site or app.

I plan to package this under https://salsa.debian.org/debian/typesense.
If there's a matching packaging team, more than happy to move there!
#1037176#10
Date:
2023-06-07 08:10:50 UTC
From:
To:
Le mer. 7 juin 2023 à 08:00, Didier 'OdyX' Raboud <odyx@debian.org> a
écrit :

It is useful for dyslexic people. Maybe accessibilty related team ?

Bastien
#1037176#15
Date:
2023-06-07 08:10:50 UTC
From:
To:
Le mer. 7 juin 2023 à 08:00, Didier 'OdyX' Raboud <odyx@debian.org> a
écrit :

It is useful for dyslexic people. Maybe accessibilty related team ?

Bastien
#1037176#20
Date:
2023-06-08 04:21:49 UTC
From:
To:
Le mercredi, 7 juin 2023, 10.10:50 h CEST Bastien ROUCARIES a écrit :

It's more of a web-oriented / mobile search engine than an accessiblity
facilitator.

That said, I've sadly noted that it build-depends on several more un-packaged
software, namely Apache brpc (which typesense forks), braft (same), lru-cache
(https://github.com/goldsborough/lru-cache/, never released), libfor (https://
github.com/cruppstahl/libfor, never released, little-endian only).

That'll be (much) more work than I expected, and I'll ponder on how to move
forward here.

Best,
    OdyX
#1037176#31
Date:
2025-12-26 03:18:27 UTC
From:
To:
Hi!

What is the status with Typesense packaging?

I see there are no commits at
https://salsa.debian.org/typesense-team/typesense/-/commits/debian/latest
since 2023, and last message in this bug report mentions upstream has
forked dependencies that are tricky to package.

Was there some feature requests for upstream to upstream their own
dependencies so no unnecessary forks are maintained long-term? I am
sure the Typesense team don't want to have too many dependencies to
fork/maintain permanently either.
#1037176#36
Date:
2025-12-26 18:17:23 UTC
From:
To:
Hello there Otto,

Le vendredi, 26 décembre 2025, 04.18:27 h Otto Kekäläinen a écrit :
when needed: https://github.com/akyriako/typesense-operator

Back when I tried to package, I quickly realised that:
- a) it was going to need a lot of build- and run-dependencies, many of which
in technologies or languages that I'm not very familiar with
- b) it's a fast-moving target: there were new dependencies needed when I
looked again after some time.
headers of an unreleased lru-cache repository, which doesn't build correctly
(at least when I tried in 2023). Also, typesense moved from CMake to bazel as
build-system, which is gone from Debian: https://lists.debian.org/debian-bazel/2023/02/msg00002.html

So, I've given up, hence my rename from ITP to RFP and my disowning of the
bugreport.

Best, and a merry end of year,

    OdyX