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
audiality2, koboredux: init #85203
audiality2, koboredux: init #85203
Conversation
282f0b5
to
7541e0a
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/160 |
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.
Very neat! Everything looks good to me. I think I can trust you that you have tested the proprietary assets, though the offer is appreciated :)
One thing to consider: We could also default useProprietaryAssets
to true
. This would
- make sure the users are getting the experience the developer intended by default
- further encourage the business model, which indeed looks very fair
We could then add another attribute, koboredux-free
, that disables the proprietary assets. It could also override meta.description
appropriately to show the relation. The error message of requireFile
could point people to the free version.
The biggest downside is that the unfree license could prevent people from even giving it a shot and seeing the error message. Those people would probably find the -free
version the same way they would have found the unfree version though.
What do you think? I don't feel very strongly about this either way. If you prefer it the way it is now, I'll merge.
@timokau that's a great idea, I'll change it.
Yes, this is a shame, I wish we had an exception or a special license attribute for this case. If the descriptions reference each other it isn't so bad though |
Yeah, I doubt many people would be bothered by unfree assets in practice (especially if there are free substitutes). Great, ping me when this is ready for another review. |
(busy times, I'll pick this up again sometimes this month) /marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. The stages are
Anybody can switch the current status with a comment of the form Feedback and contributions to this bot are appreciated. |
Well, that was a long time for a couple of string changes 😅 @timokau how about this? too pushy? |
@glittershark please review. |
/status awaiting_changes |
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.
Code LGTM besides the existing comment about the too-long description. Happy to test if necessary, but it seems like that's already been taken care of?
bfc02d4
to
82b8a47
Compare
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.
Looks good otherwise.
82b8a47
to
130ce6d
Compare
Thanks! |
Motivation for this change
Great game similar to the already packaged kobodeluxe. I think packaging also the proprietary part is fair, since in doing so we encourage a sensible foss business model. If you are a nixpkgs committer and want to test the proprietary assets, you can contact me and I'll send you a key.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)