From: David Pirotte <david@altosw.be>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Patrick Hetu <patrick.hetu@auf.org>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add guile-gnome
Date: Thu, 9 Jun 2016 16:45:52 -0300 [thread overview]
Message-ID: <20160609164552.6097b2b6@capac> (raw)
In-Reply-To: <20160609063753.GA513@debian-netbook>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
> > > ...
> > > + (modify-phases %standard-phases
> > > + (add-before 'configure 'pre-configure
> > > + (lambda* (#:key outputs #:allow-other-keys)
> > > + (let ((out (assoc-ref outputs "out")))
> > > + (substitute* (find-files "." "^Makefile.in$")
> > > + (("guilemoduledir =.*guile/site" all)
> > > + (string-append all "/2.0")))
> > > + #t))))))
> > > ...
> > Just curious: why do you (string-append all "/2.0")? Is this a guix guideline
> > maybe?
> > IMO, G-wrap, Guile-Cairo and Guile-Gnome should all be installed in the
> > directory returned by (%global-site-dir)
> `guilemoduledir =.*guile/site' is saved in the variable `all' and then
> used in the second half of the substitute*. I have a similar one I
> wrote for aria2 in bittorrent.scm
ok, but why "/2.0" is appended to it?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-09 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 18:56 [PATCH] gnu: Add guile-gnome Patrick Hetu
2016-05-28 16:06 ` Ludovic Courtès
2016-06-07 17:57 ` Patrick Hetu
2016-06-07 21:47 ` David Pirotte
2016-06-08 13:19 ` Ludovic Courtès
2016-06-08 17:34 ` Patrick Hetu
2016-06-08 20:37 ` David Pirotte
2016-06-09 6:37 ` Efraim Flashner
2016-06-09 19:45 ` David Pirotte [this message]
2016-06-10 8:44 ` Alex Kost
2016-06-11 21:54 ` David Pirotte
2016-06-10 12:52 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160609164552.6097b2b6@capac \
--to=david@altosw.be \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=patrick.hetu@auf.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.