FWIW, the GNU Project makes an argument against LGPL if you believe your software "provides a significant unique capability": https://www.gnu.org/licenses/why-not-lgpl.html
aurtzy
Auto-building menus from e.g. makefiles is a feature I'd like Disproject to support in some capacity as well in the future. I came across the transient-compile package a while back while researching ideas; might be of interest to look at.
Is this perhaps your issue? https://github.com/element-hq/element-android/issues/8881
I had a friend encounter this, and apparently it's been fixed in a recent release.
(CCing others that had the same problem: @ReversalHatchery@beehaw.org, @filibusterPerigrin@programming.dev)
I have for the past half year. I don't have numbers, but rolling with the NVK vulkan driver (context for the unaware [1]) on mesa's main branch gets me somewhere around half the proprietary driver's performance on average, and can be accompanied with stutters if it is a heavy bottleneck (turning down the resolution is an easy way out). Most games I've tried are runnable now.
It sounds like you're looking for more performance with this post though, so you're likely not going to see improvements taking this route. I would still suggest giving it a try for people that are able and can tolerate the sacrifice. It's good enough for me (and better in the wayland case) that I rarely swap to the proprietary driver anymore.
Mesa has a tracker issue for games on NVK [2] [3] with reports about game statuses and issues from the past 5 months. It includes playable and unplayable games for those interested in gauging its usability.
Also, for the record, NVK is no longer considered experimental as of mesa 24.1 (May of this year) [4].
[1] https://www.collabora.com/news-and-blog/news-and-events/nvk-has-landed.html
[3] https://gitlab.freedesktop.org/mesa/mesa/-/issues/11066
[4] https://www.collabora.com/news-and-blog/news-and-events/nvk-is-now-ready-for-prime-time.html
You might be interested in git-annex (see the Bob use case).
It has file tracking so you can - for example - "ask" a repository at drive A where some file is, and git-annex can tell you it's on drives C and D.
git-annex can also enforce rules like: "always have at least 3 copies of file X, and any drive will do"; "have one copy of every file at the drives in my house, and have another at the drives in my parents' house"; or "if a file is really big, don't store it on certain drives".
You're reading the manual for Guix 1.4.0, which was released more than a few years ago! You might find the development version of the manual more helpful for documentation on plasma-desktop-service-type: https://guix.gnu.org/manual/devel/en/html_node/Desktop-Services.html#index-plasma_002ddesktop_002dservice_002dtype
I have Plasma configurations here, although it's been a while since I've used them (am on GNOME at the moment): https://github.com/aurtzy/guix-config/blob/master/modules/my-guix/mods/desktop-environment.scm#L110
Also, if you downloaded the 1.4.0 installer, you might have to guix pull (so the current state of Guix's plasma is made available) before trying to do any reconfiguring.