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
lilyterm-git: init at 2017-01-06 #23327
Conversation
@Profpatsch, thanks for your PR! By analyzing the history of the files in this pull request, we identified @AndersonTorres and @wkennington to be potential reviewers. |
The latest stable release is quite old (2013-02) and many improvements have been made in the meantime.
The failing build is unrelated. |
I need to create a plan for testing it. Tomorrow I will run it! |
, pkgconfig | ||
, autoconf, automake, intltool, gettext | ||
, gtk, vte }: | ||
, gtk, vte | ||
|
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.
Why that whitespace?
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.
To separate the the “manual” arguments from the “automatic” ones (i.e. included by callPackage by default).
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.
OK!
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.
Tested and works great.
Will merge, thanks for the reviews. |
|
||
stdenv.mkDerivation rec { | ||
# "stable" or "git" | ||
, flavour ? "stable" |
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.
About that line normally I would put the option description in the same line, after the parameter itself (except if it was something more elaborate).
It is more natural to read that way: flavour ? "stable" # options: git, stable
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.
Well, that’s a pretty minor choice of style I’d say.
The latest stable release is quite old (2013-02) and many improvements have been
made in the meantime.
New version builds, old version evaluates to the same store path.