Package Details: vodozemac-bindings-cpp-kazv 0.1.0-3

Git Clone URL: https://aur.archlinux.org/vodozemac-bindings-cpp-kazv.git (read-only, click to copy)
Package Base: vodozemac-bindings-cpp-kazv
Description: kazv's C++ bindings for the vodozemac cryptographic library.
Upstream URL: https://lily-is.land/kazv/vodozemac-bindings
Licenses: Apache-2.0
Submitter: shrik3
Maintainer: shrik3
Last Packager: shrik3
Votes: 0
Popularity: 0.000000
First Submitted: 2024-10-19 20:02 (UTC)
Last Updated: 2024-11-13 14:56 (UTC)

Latest Comments

shrik3 commented on 2024-11-14 16:00 (UTC) (edited on 2024-11-14 16:04 (UTC) by shrik3)

dreieck:

It is a rust library anyway, and I have no idea how to make a "C" shared library from this.

sorry, I gave the wrong reference. The upstream is https://github.com/matrix-org/vodozemac-bindings which is officially "unmaintained". It's a binding for other languages, not the library itself.

I had a brainfart, sorry for the misinformation.

RT: https://aur.archlinux.org/packages/vodozemac-bindings-cpp-kazv#comment-998355

dreieck commented on 2024-11-13 16:08 (UTC)

Addendum:

I was wondering whether this package should provide libvodozemac at all: kazv's fork (this) differs from the original [1] a lot and has different versioning.

In this case I think it should not provide libvodozemac at all.

But maybe it still should conflicts=('libvodozemac'), because it installs /usr/include/vodozemac.h and /usr/lib/libvodozemac.so*.

dreieck commented on 2024-11-13 13:56 (UTC) (edited on 2024-11-13 13:58 (UTC) by dreieck)

I was wondering whether this package should provide libvodozemac at all: kazv's fork (this) differs from the original [1] a lot and has different versioning.

In this case I think it should not provide libvodozemac at all.

[1] https://github.com/matrix-org/vodozemac ; which AFAIK is not packaged for arch.

It is a rust library anyway, and I have no idea how to make a "C" shared library from this.

Does kazv's fork forkes and changes https://github.com/matrix-org/vodozemac as well, or does it only provide a wrapper to build a shared "C" library? Ok, seems the first. :-(.

Thank you for the maintanance!

shrik3 commented on 2024-11-12 20:16 (UTC) (edited on 2024-11-14 16:06 (UTC) by shrik3)

@dreieck :

You can (and should) remove rust from makedepends once you have cargo

done;

I see strange versioned provides entry in the finished build [SNIP..]

I'm new to packaging and this is my mistake; I'll commit the changes in a few days. Thanks for pointing out.

other than that, I was wondering whether this package should provide libvodozemac at all: kazv's fork (this) differs from the original [1] a lot and has different versioning.

[1] https://github.com/matrix-org/vodozemac-bindings ; which AFAIK is not packaged for arch.

P.S. I've pointed the devs to your notes on libkazv-git and kazv-git. Thank you!

[EDIT] I wrongly pointed to the vodozemac library as upstream. It should have been the bindings, which is unmaintained.

dreieck commented on 2024-11-12 18:37 (UTC)

I see strange versioned provides entry in the finished build:
libvodozemac.so=0.1.0 and libvodozemac.so=libvodozemac.so-64.

The first version is manually specified in the provides array (I think it should have a -<bitdepth> suffix, calculated from $CARCH?), the second one is strange, though.

Anyway, I suggest to add libvodozemac to the provides and conflicts arrays (and libvodozemac.so maybe too to the conflicts array).

Regards!

dreieck commented on 2024-11-12 18:04 (UTC) (edited on 2024-11-12 18:08 (UTC) by dreieck)

I thought cargo was already provided by rust

It is, but rust was neither a makedependency.

I thing (observing other packages) specifiyng cargo is the correct way, and usually this results in installing rust, but if people need specific other versions like rustup they also can install that.

You can (and should) remove rust from makedepends once you have cargo, otherwise you could create conflicts with rustup, cargo-nightly or so, I think.
But I am really unsure on this aspect!

shrik3 commented on 2024-11-11 20:30 (UTC)

@dreieck :

both done, thanks for the comments.

I thought cargo was already provided by rust; my bad.

dreieck commented on 2024-11-11 19:41 (UTC)

I am now trying to build this in order to bring libkazv-git up to date.

cargo needs to be added to the makedepends array:

make: cargo: No such file or directory

When done, please rework your PKGBUILD so that the rust specific downloads already happens in prepare():

    Updating git repository `https://github.com/matrix-org/vodozemac/`
    Updating crates.io index
  Downloaded matrix-pickle v0.2.1
  Downloaded thiserror-impl v1.0.63
  Downloaded termcolor v1.4.1
  Downloaded scratch v1.0.7
  Downloaded rustc_version v0.4.1
  Downloaded prost-derive v0.13.2
  Downloaded link-cplusplus v1.0.9
  Downloaded cxxbridge-flags v1.0.128
  Downloaded cpufeatures v0.2.14
  Downloaded matrix-pickle-derive v0.2.1
  Downloaded itoa v1.0.11
  Downloaded getrandom v0.2.15
  Downloaded prost v0.13.2
  Downloaded cbc v0.1.2
  Downloaded semver v1.0.23
  Downloaded flagset v0.4.6
  Downloaded version_check v0.9.5
  Downloaded pkcs7 v0.4.1
  Downloaded either v1.13.0
  Downloaded ppv-lite86 v0.2.20
  Downloaded thiserror v1.0.63
  Downloaded subtle v2.6.1
  Downloaded zerocopy-derive v0.7.35
  Downloaded der_derive v0.7.3
  Downloaded ryu v1.0.18
  Downloaded arrayvec v0.7.6
  Downloaded once_cell v1.20.0
  Downloaded bytes v1.7.1
  Downloaded anyhow v1.0.89
  Downloaded codespan-reporting v0.11.1
  Downloaded unicode-ident v1.0.13
  Downloaded indexmap v2.5.0
  Downloaded der v0.7.9
  Downloaded cxxbridge-macro v1.0.128
  Downloaded x509-cert v0.2.5
  Downloaded memchr v2.7.4
  Downloaded cc v1.1.19
  Downloaded cxx-build v1.0.128
  Downloaded zerocopy v0.7.35
  Downloaded serde_json v1.0.128
  Downloaded itertools v0.13.0
  Downloaded cxx v1.0.128
  Downloaded syn v2.0.77
  Downloaded unicode-width v0.1.13
  Downloaded libc v0.2.158
  Downloaded 45 crates (3.5 MB) in 8.54s

Regards and thanks for the package!