Search Criteria
Package Details: python-hnswlib 0.9.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/python-hnswlib.git (read-only, click to copy) |
|---|---|
| Package Base: | python-hnswlib |
| Description: | Header-only C++/python library for fast approximate nearest neighbors |
| Upstream URL: | https://github.com/nmslib/hnswlib |
| Licenses: | Apache-2.0 |
| Submitter: | a821 |
| Maintainer: | a821 |
| Last Packager: | a821 |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2021-12-20 20:45 (UTC) |
| Last Updated: | 2026-03-29 07:05 (UTC) |
Dependencies (9)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- libgcc (libgcc-snapshotAUR)
- libstdc++ (libstdc++-snapshotAUR)
- python-numpy (python-numpy-gitAUR, python-numpy-mkl-binAUR, python-numpy1AUR, python-numpy-mkl-tbbAUR, python-numpy-mklAUR)
- pybind11 (pybind11-gitAUR) (make)
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
Required by (5)
- gundog
- hnswlib (optional)
- hnswlib-git (optional)
- python-opentsne (optional)
- python-opentsne-git (optional)
Latest Comments
a821 commented on 2026-04-01 07:26 (UTC)
@vitaliikuzhdin: Hi, thanks for the offer but no thanks. I rather keep both packages independent.
The issue here is that the library and the python bindings are two independent builds, and then don't even depend on each other.
I looked at your proposed
PKGBUILDand you are basically copy-pasting mine into yours. This provides no advantage. Also, this causes inconveniences when you just need one of them. i.e., if I just need the python package, why should I compile the library, or if I need the library, why I should be bothered compiling the python bindings. And I think this does not even simplify the maintenance, you still need to check that both of them work.IMHO, split packages don't really make sense in the AUR unless there is only one build process (libs and programs separated in
package), or at least one is a dependency of the other, or they're tightly coupled. None of these are the case here. (I'd like to emphasize I'm referring to the AUR, split official packages is another story).And a side note to illustrate my point, this reminds me of the split
python2andpython3packages in the AUR back in the day; you had to install/compile a bunch ofpython2packages and then immediately delete them just to get thepython3version (I ended up forking thePKGBUILDin those cases... really forking annoying).All in all, I strongly believe this will make everything more complicated, so let's keep them separated.
vitaliikuzhdin commented on 2026-03-31 15:31 (UTC) (edited on 2026-03-31 15:44 (UTC) by vitaliikuzhdin)
Hello, can we agree to merge this into hnswlib to have 2
pkgnames from a singlepkgbase? It will be easier to maintain and keep the build process in sync, see myPKGBUILDfor more details. Of course, I will make you a co-maintainer or transfer the ownership entirely, if you'd like.