-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
jabcode: init at git-2020-05-13 #92697
Conversation
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
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.
Some small nitpicks. I'm curious: Is there any real use-case for this already? What's your motivation in packaging this?
|
||
preConfigure = "cd src/${subdir}"; | ||
|
||
installPhase = if subproject == "library" then '' |
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.
It seems like the library really should be its own derivation, it shares little code with the reader/writer.
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.
Not sure about that, it does share the source as well as some of the build inputs. Also since its all in the same repo upstream, if they decide to e.g. make changes to the build system at some point, they could become more coupled in the future.
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.
If you feel strongly about this, I can decouple them
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.
No, I don't feel very strongly. I think dependencies are likely to diverge, but your points are valid as well.
Thanks for reviewing this! Currently its mostly for playing around with it. But I hope that the library part can be reused in |
Alright, probably the purest of open-source motivations :) Thanks for the contribution! |
Motivation for this change
jabcode
consists of a library and reader/writer executables for the JAB bar code format. It constitutes the reference implementation of what will be an ISO standard (NP23634).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)