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
solaar: add unreleased but supported master branch version #43991
Conversation
@@ -0,0 +1,42 @@ | |||
{fetchFromGitHub, stdenv, gtk3, python34Packages, gobjectIntrospection}: | |||
python34Packages.buildPythonApplication rec { | |||
name = "solaar-${version}"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the name part should be solaar-unstable
and the version part should be the date, YYYY-MM-DD
https://nixos.org/nixpkgs/manual/#sec-package-naming
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the age of the current release it might be better to upgrade the current stable package to master rather maintaining two packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thats what I thought as well
would we go and remove that stable package or alter it to point to the master branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just point it to master.
propagatedBuildInputs = [python34Packages.pygobject3 python34Packages.pyudev gobjectIntrospection gtk3]; | ||
postInstall = '' | ||
wrapProgram "$out/bin/solaar" \ | ||
--prefix PYTHONPATH : "$PYTHONPATH" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--set PYTHONPATH
typically has preference, since otherwise you may break your application if you have some PYTHONPATH
set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you mean
wrapProgram "$out/bin/solaar" \
--set PYTHONPATH : "$PYTHONPATH" \
?
I would say that we should just replace the old version with this. We don't want to duplicate packages more than already is done. Very weird that they have not made a release though. Maybe open an issue about it? |
src = fetchFromGitHub { | ||
owner = "pwr"; | ||
repo = "Solaar"; | ||
rev = "master"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a tag or commit that will not change. This hash will change each time with master.
@GrahamcOfBorg build solaar |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: solaar Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: solaar Partial log (click to expand)
|
Looks like there is some recent talk of forking the project pwr-Solaar/Solaar#407 |
Success on aarch64-linux (full log) Attempted: solaar Partial log (click to expand)
|
@ryantm |
Sure. I squashed and merged it. |
Motivation for this change
Having a Logitech MX Master 2x I the current upstream version of solaar is needed. As there are no version steps for a long time I named this one master and kept the existing solaar package which tracks releases.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)