Package Details: reflective-rapidjson 0.0.10-1

Git Clone URL: https://aur.archlinux.org/reflective-rapidjson.git (read-only)
Package Base: reflective-rapidjson
Description: Code generator for serializing/deserializing C++ objects to/from JSON using Clang and RapidJSON
Upstream URL: https://github.com/Martchus/reflective-rapidjson
Licenses: GPL
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 1
Popularity: 0.000027
First Submitted: 2018-01-27 14:28
Last Updated: 2019-10-12 21:55

Pinned Comments

Martchus commented on 2018-01-31 19:55

All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs There also exist a binary repository: https://martchus.no-ip.biz/repo/arch/ownstuff

Latest Comments

1 2 Next › Last »

petef4 commented on 2019-10-13 18:48

@Martchus Option 2 worked for me, thanks.

Martchus commented on 2019-10-13 16:37

@petef4 There is no cycle. reflective-rapidjson simply needs a certain LLVM version and that's it.

Ok, that's not it: Of course installing LLVM 9 will break "the old" reflective-rapidjson which still needs LLVM 8 but building a new version of reflective-rapidjson requires LLVM 9. The recommended way to solve this problem is to build with makechrootpkg. This is how the official packages are created (see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot). I'm also using this method to build the packages provided by my binary repository.

There are also 2 lazy ways to work around this issue:

  1. Use my binary repo.
  2. Uninstall reflective-rapidjson. Install LLVM 9. Build reflective-rapidjson again.

Note that 2. only works well for reflective-rapidjson because nothing depends on it (it is only a build-time dependency for tageditor!). In the general case uninstalling the package is of course annoying because a lot packages might depend on it (consider the packages x265 and ffmpeg/ffmpeg-libfdk_aac which have basically the same problem but you likely don't want to uninstall ffmpeg on your system).

petef4 commented on 2019-10-13 16:24

I suspect that this is a pacman FAQ. reflective-rapidjson will not update 0.0.9-1 -> 0.0.10-1 because it needs llvm-libs>=9.0.0. But llvm-libs will not update because it is needed by the old reflective-rapidjson: llvm-libs (9.0.0-3) breaks dependency 'llvm-libs<9.0.0' required by reflective-rapidjson. What is the best way to resolve this cycle?

Martchus commented on 2019-09-28 13:29

Partial updates are not supported. I will never update only one of the packages in a way it would break compatibility. The Arch way is to keep it simple so I'm reluctant to take effort to solve a problem which does not exist.

shillshocked commented on 2019-09-28 11:58

c++utilities 5.0.0+ should be a dependency requirement. Currently there is no version requirement.

Martchus commented on 2019-03-27 14:46

Sorry, I've pushed this too early. This should build as soon as llvm/clang 8 is released from staging.

luka-devnull commented on 2018-10-13 09:09

The checksum that failed wasn't for the patch file, it was for the reflective-rapidjson-0.0.5.tar.gz file:

sha256sum reflective-rapidjson-0.0.5.tar.gz
3ba7c7f2a73c9ab2afe38cd884b8f1290e770f17c9fd497de5468c7d4a690bdb  reflective-rapidjson-0.0.5.tar.gz

The checksum you provided was 7de997399332b723810833756c39b97e2ffa4160d5453ce1e2af6b4f5f4f90a7, which is invalid.

Martchus commented on 2018-10-08 11:27

I have already fixed the checksum once and it still seems valid:

wget https://github.com/Martchus/reflective-rapidjson/commit/5835cd85a5bbc72f4ac47a81b09e986cc8dee715.patch
sha256sum 5835cd85a5bbc72f4ac47a81b09e986cc8dee715.patch 
958dc1902d9a6d245ce198ccdf02ffd3049404e0a5446892ce55db0108baa888  5835cd85a5bbc72f4ac47a81b09e986cc8dee715.patch

clpwn commented on 2018-10-08 03:00

SHA256 appear to be invalid.

==> Validating source files with sha256sums... reflective-rapidjson-0.0.5.tar.gz ... FAILED 5835cd85a5bbc72f4ac47a81b09e986cc8dee715.patch ... Passed ==> ERROR: One or more files did not pass the validity check!

Martchus commented on 2018-09-28 07:40

How should I know how to tell your (stupid) AUR helper to exclude a package :-)

BTW, I recommend to build in a clean chroot like the official devs do. This allows you to build right now against staging and install the package locally when LLVM is released from staging.