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
python3Packages.elgato: init at 2.1.1 #126047
Conversation
Please update this PR. |
As the author of this package, I would request not to repack my code in this case. Thank you for honoring the authors wishes. |
Locked for now. Please see #126677 (comment). |
As the author of the upstream package, I do not agree with this package being added. While licensing wise I cannot stop you at this point, I think the way it is used and packaged in this project harms the user experience and thus the upstream project. Thank you for considering. |
@frenck I don't want to sound rude, but sorry, then you need to change your license. Is this truly an open source or a proprietary software indeed? There is nothing bad in adding this package to nix collection. On the contrary, it only gives it popularization, and most importantly, helps other people. People who use this package in Nix/NixOS would not disturb you in any manner related to the packaging in our system. |
[This is all my personal opinion and not the position of "The NixOS Project" or anything like that] We've had discussions about this - in a few other issues, for other HA dependencies authored by frenck; authors of software are free to express their wishes above and beyond what the license they've chosen actually requires, and as part of the OSS ecosystem it's our responsibility to listen to and consider those requests. We should remain respectful of these requests and the human beings behind them, even if we ultimately choose not to abide by them. For better or for worse, in NixOS "we've" decided to continue to try to package this software: in NixOS, we provide a different user experience for HA than upstream provides as a result of our declarative-configuration philosophy, and as a result as responsible members of the OSS ecosystem we need to do our part in trying to reduce the support load on upstream - we expect that users of NixOS who use the HA packaging we provide will be aware of these implications (because, well, they're users of NixOS: they're probably used to things being a little different), and that there are clear escape hatches if they choose to run HA in an upstream-supportable way (using The HA ecosystem is large, and the team can't possibly understand and make everything work every weird configuration that users throw at them, so I harbour no ill will towards them for wanting to reduce the scope of configurations that they're willing to support, and am extremely grateful for all the work they, and other OSS maintainers, put into providing this software for everyone to use for free. [This is all my personal opinion and not the position of "The NixOS Project" or anything like that] |
We know this. Please stop posting this under new packages or updates here. Thank you. |
Thanks, I'm aware you know this, someone looking into the history might not. Thanks 👍 ../Frenck |
Motivation for this change
Python client for Elgato Key Lights
https://github.com/frenck/python-elgato
This is a Home Assistant dependency.
ToDo:
component-packages
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)