From: Leo Famulari <leo@famulari.name>
To: gno <gnopap@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: awesome: Add awesome-3.5
Date: Tue, 30 Aug 2016 02:56:10 -0400 [thread overview]
Message-ID: <20160830065610.GC4193@jasmine> (raw)
In-Reply-To: <20160825030933.06c8d523@gmail.com>
On Thu, Aug 25, 2016 at 03:09:33AM +0200, gno wrote:
> Sure hope I'm doing this right as I'm new to this.
> These patches add Awesome 3.5.9 to the repository. I decided against
> updating since it may break peoples configurations. Awesome had API
> changes in between 3.4 and 3.5.
>
> Please have a look.
Thanks for these patches! We need to figure out the Lua issue, and I've
replied in the Lua / Prosody thread.
> Subject: [PATCH 2/3] gnu: lua: Add lua-lgi.
>
> * gnu/packages/lua.scm (lua-lgi): New variable.
> + (replace 'configure
I think we should just delete the configure phase if there is no
'./configure' script.
> + (lambda* (#:key inputs #:allow-other-keys)
> + ; needs to load cairo dynamically
> + (let* ((cairo (string-append
> + (assoc-ref inputs "cairo") "/lib" )))
> + (setenv "LD_LIBRARY_PATH" cairo ))
This can go in a 'set-env' phase.
> +
> + ; FIXME: Skip GTK tests:
> + ; gtk3 - can't get it to run with the xorg-server config below
> + ; and some non-gtk tests will also fail
> + ; gtk2 - lots of functions aren't implemented
> + ; We choose gtk2 as the lesser evil and simply skip the test.
> + ; as of 22/08/2016 awesome is the only package dependent on lgi but
> + ; it doesn't need or interact with gtk using lgi.
> + (substitute* "./tests/test.lua"
> + (("'gtk.lua',") "-- 'gtk.lua',"))
This should go in a 'disable-tests' phase.
> + ; lua version and therefore install directories are hardcoded
> + (substitute* "./lgi/Makefile"
> + (("LUA_VERSION=5.1") "LUA_VERSION=5.2"))
Again, in its own phase. I'm not sure what to call it :)
> + ;; There must be a running X server during tests.
> + (system (format #f "~a/bin/Xvfb :1 &" (assoc-ref inputs "xorg-server")))
> + (setenv "DISPLAY" ":1"))))
This should go in a phase with a name like "start-x-server' before the
check phase.
> + #:make-flags
> + (let ((out (assoc-ref %outputs "out")))
Is binding this 'out' variable necessary when it gets recreated in the
string-append below?
> + (list "CC=gcc"
> + (string-append "PREFIX=" (assoc-ref %outputs "out"))))))
> Subject: [PATCH 3/3] gnu: wm: Add awesome-3.5.
>
> * gnu/packages/wm.scm (awesome-3.5): New variable.
> +(define-public awesome-3.5
> + (package (inherit awesome)
> + (version "3.5.9")
Is there upstream support for the 3.4 series? We shouldn't keep it if
it's unsupported, in my opinion.
> + (snippet
> + ;; Remove non-reproducible timestamp and use the date of the
> + ;; source file instead.
Thanks for paying attention to this issue. Our unwritten convention is
to take the value of the environment SOURCE_DATE_EPOCH. Can you do that
instead? There are examples in the Erlang package if you need them.
Thanks again for these patches!
Let's fix our Lua packaging. And, can you send revised versions of
patches 2 and 3 from this series?
next prev parent reply other threads:[~2016-08-30 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 1:09 [PATCH] gnu: awesome: Add awesome-3.5 gno
2016-08-25 9:22 ` ng0
2016-08-25 9:37 ` ng0
2016-08-25 9:59 ` ng0
2016-08-25 14:47 ` ng0
2016-08-25 17:26 ` doncatnip
2016-08-26 13:33 ` ng0
2016-08-26 15:19 ` doncatnip
[not found] ` <20160825172521.19de318e@gmail.com>
2016-08-25 14:50 ` ng0
2016-08-25 17:24 ` doncatnip
2016-08-30 6:56 ` Leo Famulari [this message]
2016-08-30 8:52 ` gno
2016-08-30 18:26 ` 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=20160830065610.GC4193@jasmine \
--to=leo@famulari.name \
--cc=gnopap@gmail.com \
--cc=guix-devel@gnu.org \
/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).