- As polymc has been hostily taken over, prismlauncher (the fork) should
be used instead
- The previous commit packages prismlauncher, this commit makes it so
that installing polymc will give an error message
This reverts commit d06207386d.
Removing aliases without warning is not ok, because it breaks a
lot of third party code, without a grace period during which the
ecosystem can adapt.
This reverts commit ba3319568d.
Removing aliases without warning is not ok, because it breaks a
lot of third party code, without a grace period during which the
ecosystem can adapt.
https://discourse.gnome.org/t/split-and-rename-of-chrome-gnome-shell/11075815ec9e1af...v42.0
- Renamed and split into a separate repo from the extensions.
- CMake build replaced with Meson (jq also not needed)
- requests Python module not needed since updates are now solely handled by GNOME Shell itself
Also
- Corrected license
- Cleaned up the module
- Replaced PYTHONPATH in a wrapper by Python environment
Changelog-Reviewed-By: Jan Tojnar <jtojnar@gmail.com>
The package fails t install as it requires x86_64-linux, but it's
dependency requires i686 linux:
$ nix build --no-link -f. timedoctor --show-trace
error: unsupported CPU i686
… while evaluating the attribute 'version'
at pkgs/development/compilers/adoptopenjdk-bin/jdk-linux-base.nix:40:3:
39|
40| version = sourcePerArch.${cpuName}.version or (throw "unsupported CPU ${cpuName}");
| ^
I only onticed it because it uses `xorg.libXaw3d` while nothing else does.
Let's remove it.
Multipath tcp (mptcp) is now part of the official linux kernel. The
official kernel still lacks features compared to this out of tree ones
but considering the userbase, I dont see any compelling reason.
I keep using that kernel and those utilities so they will stay packaged
at https://github.com/teto/mptcp-flake where they wont annoy the whole
nixpkgs crowd that doesn't care about it.
This project has reached its end of life, the repository is marked as an
archive. Its recommanded to use the already packaged `cider` instead.
Fixes#193593
The package was introduced when our source package did not expose
libtensorflow, which it does these days. Additionally the -bin package
has not been well maintained and is stuck on a version from 2020/12.
