Kirottu
Upstream Home Manager module to Home Manager
Anyrun is already packaged in Nixpkgs. Why don't upstream its Home Manager module to Home Manager? Users will be able to use Anyrun without fetching external flake and without building Anyrun from source.
I do not like how long it takes to get simple contributions into home-manager, and I also stopped using home-manager a while ago. I believe @khaneliman has received the commit bit in HM repository, and is involved in Anyrun packaging, perhaps he would be interested in adding a module? Otherwise anyone is free to try and upstream it by themselves.
This is great that it has been merged into home manager, do we still need the anyrun flake to install plugins with it, or is that now possible via nixpkg and homemanager? Sorry if it's obvious but I couldn't figure out how.
Perhaps we could put core anyrun plugins into Anyrun's passthru?
Ithink we are going back on putting core plugins into separate repositories, so we might be able to put them in the anyrun package (or something to expose them as a package,e.g., anyrunWithPlugins) to make them available. Alternatively we might be able to consider adding a scope like anyrunPlugins.
The nixpkgs anyrun package includes plugins under $out/lib but that is definitely not ideal.
Currently I have to do this:
...
programs.anyrun = {
enable = true;
package = pkgs.anyrun;
config = {
plugins = [
"${pkgs.anyrun}/lib/libapplications.so"
"${pkgs.anyrun}/lib/librink.so"
"${pkgs.anyrun}/lib/libsymbols.so"
"${pkgs.anyrun}/lib/libwebsearch.so"
];
...
};
...
};
...
Am I wrong in some way (could be, am new to Nix) or is an HM module already upstreamed for Anyrun? Recently started messing around with Nix and finally realized I was using the upstreamed HM module all along.
So is this issue still relevant?
