-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Minor coding style fix: lib.getExe instead of ${bin}/bin/bin #391
Conversation
43135c6
to
8d14944
Compare
Looks good. Thanks for this cleanup! One minor thing: can you fix your commit names to match the style of the other commits in the repository? Will merge afterwards! |
@blitz I believe that everything could be squashed into a single commit. (I was a bit too verbose while making the commits). Would it be fine if I squashed everything into a single commit? I am currently away, so I will take care of it ~8h later |
Sure. One commit is fine. 👍 |
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.
LGTM modulo commit messages.
Alright, should be fine now |
@blitz is the commit name alright? |
flake: add meta.mainProgram attribute to wrappedTool (lzbt)
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.
Thank you for taking the time to do this!
This is a minor change in coding style that removes path references replacing them with
lib.getExe
.This makes executable references less dependent on binary names.
Major advantage: the
cfg.package
option doesn't require the binary name to be "lzbt" anymore.