From: Leo Famulari <leo@famulari.name>
To: Mekeor Melire <mekeor.melire@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add dzen.
Date: Mon, 13 Feb 2017 19:41:21 -0500 [thread overview]
Message-ID: <20170214004121.GA21528@jasmine> (raw)
In-Reply-To: <20170214002828.4311f801@gmail.com>
On Tue, Feb 14, 2017 at 12:28:28AM +0100, Mekeor Melire wrote:
> From 04f94c306f99a7bacc96b60ed60e9bb83a9cf767 Mon Sep 17 00:00:00 2001
> From: Mekeor Melire <mekeor.melire@gmail.com>
> Date: Tue, 14 Feb 2017 00:21:08 +0100
> Subject: [PATCH] gnu: Add dzen.
>
> * gnu/packages/xdisorg.scm (dzen): New variable.
Thanks!
> +(define-public dzen (package
'(package ...' should start on the second line, underneath the 'e' of
'define'.
There is a script 'etc/indent-code.el' in our Git repo that should
handle indentation for you.
> + (version "0.9.5")
The version string should be constructed as shown in the manual section
'Version Numbers':
https://www.gnu.org/software/guix/manual/html_node/Version-Numbers.html#Version-Numbers
This ensures that we can distinguish between different versions of
packages that are created from version control snapshots.
> + (synopsis "General purpose messaging, notification and menuing program for X11")
> + (description "Dzen is a general purpose messaging, notification and menuing
> +program for X11. It was designed to be fast, tiny and scriptable in any language.")
> + (home-page "https://github.com/robm/dzen")
> + (license license:x11)
It's actually the Expat license:
http://directory.fsf.org/wiki/License:Expat
Also, these fields typically go at the end of the package definition. It
makes no difference technically, but adhering to a common standard helps
reading and understanding the package.
> + #:tests? #f
We must leave a comment explaining why tests are disabled. If there are
no tests, then "No test suite." is enough.
> + ; use our make-flags instead of `config.mk`
> + #:make-flags (list
> + (string-append "VERSION = " ,version)
> + (string-append "PREFIX = " %output)
> + "MANPREFIX = ${PREFIX}/share/man"
> + "INCS = -I."
> + "LIBS = -lc -lX11 -lXinerama -lXpm $(shell pkg-config --libs xft)"
> + "CFLAGS = -Wall -Os ${INCS} -DVERSION=\\\"${VERSION}\\\"\
> + -DDZEN_XINERAMA -DDZEN_XPM -DDZEN_XFT $(shell pkg-config --cflags xft)"
I don't think we should use the shell, but instead use (assoc-ref) and
(string-append) to get the right path.
> + #:phases (modify-phases
> + %standard-phases
> + ; do not `./configure`
Instead, how about "No ./configure script.", since it communicates more
clearly why we delete this phase.
next prev parent reply other threads:[~2017-02-14 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 23:28 [PATCH] gnu: Add dzen Mekeor Melire
2017-02-14 0:41 ` Leo Famulari [this message]
2017-02-22 0:10 ` Mekeor Melire
2017-03-02 2:34 ` Leo Famulari
2017-03-02 2:35 ` Leo Famulari
2017-03-02 23:25 ` Mekeor Melire
2017-03-02 23:51 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170214004121.GA21528@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mekeor.melire@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).