Arch Linux User Repository

Please stop flagging Dendrite out of date because helm-dendrite-0.12.3 is out. The "3" is a minor change of the helm chart, not the dendrite source code. The latest dendrite version is still Dendrite 0.12.0, the one with the changelog.

Please stop flagging Dendrite out of date because helm-dendrite-0.12.3 is out. The "3" is a minor change of the helm chart, not the dendrite source code. The latest dendrite version is still Dendrite 0.12.0, the one with the changelog.

@kwheelans Thank you, it should work now

Hi,

When upgrading build() failed for dendrite 0.12.0-1 with "rm: cannot remove '../cmd/dendrite-polylith-multi/': No such file or directory"

This line 'rm -r "../cmd/$pkgname-polylith-multi/"' can be removed as polylith mode has been removed from dendrite as of v0.12.0.

Hello, I think we can try to build all the components which are in the cmd directory, just like what build.sh does. See this for more info: https://github.com/matrix-org/dendrite/blob/main/build.sh

thanks for your explanation. But I think we can do minimal modification to the default configuration. I want the default configuration since it contains many explanatory comments, and when the config file changes, I can use pacdiff to see and merge the differences. But with the generated config file, it is really hard to know what is changed in the updated version, and it's difficult to add new options (since it is not contained in this config file)

And we can add a declaration in the install script that manually intervention is needed so that users know how to update the configuration (see pacman/Pacnew and Pacsave )

@sukanka in this case it is better to don't do that because the default configuration in GitHub uses different paths than the ones this package expects, so it cannot be used without editing it first.

I removed the prepare() function because it may break something if a new configuration format is released.

I guess we cannot generate the configuration during the package creation because execution of the executable may be blocked (e.g. "/tmp/makepkg/.../dendrite-generate-config" cannot be run). In this case they can only be run once extracted in the final system (e.g. "/usr/bin/dendrite-generate-config").

That's why in the .install file I reccomend to generate the configuration only after the package is installed in the machine, specifying the "--dir" and "--private-key" options.

I think the config name may be named config.yaml and add backup=('etc/dendrite/config.yaml') to PKGBUILD, see PKGBUILD#backup

I think the config filename needs to be updated to $pkgname-sample.monolith.yaml

The service should include LimitNOFILE=65536.