Providing the whole set by default is not feasible, and anything
smaller than that would be too arbitrary.
The aliases.nix error message puts users on the right path to get
exactly the plugins they need.
nixops_unstable_full probably won't be in a buildable state, so
we can't recommend it. It may be useful for CI.
flashprog, formerly flashrom-stable, got separated and is its own
project now. Thus, rename the formerly known package flashrom-stable to
flashprog and adjust all references and meta data.
Update to the newest available release 1.0.1.
Signed-off-by: Felix Singer <felixsinger@posteo.net>
This package currently uses an unsupported version of OpenSSL. The update seems simple enough, but I no longer use the package, and don't have the environment to test it anymore
If someone else adopts the package please feel free to reject this
The `zfs` alias already has equivalent semantics. Instead, make this
like zfs_2_1 so folks who want to pin a specific release series can do
so easily and clearly to have more control over when more substantial
updates occur.
Rename all tests to match the pkg attr they are testing.
Upstream calls it Bitwarden Desktop, and we have other “bitwarden-*”
packages, so having an unsuffixed one can be confusing.
I assume the hash for cargoDeps is changing since it encodes the pname.
Ada depencencies musst be build with the same gnat version as the
project. Use a namespace as preperation to build with different gnat
versions.
gprbuild and gnatprove are still globaly visable.
Gnatprove is the tool distributed out of the spark2014 repository.
AdaCore, the developer behind it, distribute it under the name gnatprove
in the Ada alire package repository [0].
Rename the package to keep in line with other distribution channels.
[0] https://alire.ada.dev/crates/gnatprove
Since picom v11 there is no more reason to keep a separate picom
derivation that tracks the `next` branch from upstream since the current
release is basically the `next` branch.
Also, picom-next right now is pointing to an old commit, so it is clear
that nobody is maintaining it updated.
If there is a necessity later, we can bring back the picom-next again.
