New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dwm-status: init at 0.4.0 #41726
dwm-status: init at 0.4.0 #41726
Conversation
It looks like there is already another project by this name packaged by AUR and crates.io https://repology.org/metapackage/rust-dwm-status/versions https://github.com/pierrechevalier83/rust-dwm-status. Can you comment on why yours has the same name, how it differs, and if you are planning to publish it to crates.io too? |
Thats not correct. The package you mentioned has the name The difference to |
@GrahamcOfBorg build dwm-status |
Success on x86_64-linux (full log) Attempted: dwm-status Partial log (click to expand)
|
Failure on x86_64-darwin (full log) Attempted: dwm-status Partial log (click to expand)
|
@ryantm Do you have an idea how to fix the error on darwin? |
Failure on aarch64-linux (full log) Attempted: dwm-status Partial log (click to expand)
|
@Gerschtli It looks like it is missing inotify. I don't know if that exists on Darwin. Are you expecting
If it
|
c1445d3
to
212b5f7
Compare
You are right, I don't expect this package to be run on Darwin, fixed it |
And the aarch64 build failure is caused by the usual timeout with rust packages.. |
@GrahamcOfBorg build dwm-status |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: dwm-status Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: dwm-status Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: dwm-status Partial log (click to expand)
|
Thank you for the package. It looks nice and I'll probably give it a shot soon :) Have you considered declaring the runtime dependency "xsetroot" in the package? It probably only works (on NixOS) because the xserver module puts that binary in the system path. If you are running dwm-status on any non-nixos system that is using nix that will probably fail (unless it is in the PATH by accident). |
That sounds reasonable, Thank you! |
Motivation for this change
Inits my own
dwm-status
package at version 0.4.0.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)