Ludovic Courtès (2015-10-08 14:46 +0300) wrote:
[...]
> The command to call ‘package-source-derivation’ for the package at point
> is still welcome, though. :-)
Thanks, here it is.
‘build-package-source’ procedure (as I see it) is very similar to
‘build-package’, so maybe it is worth to make a
Cyril Roelandt skribis:
> On 09/27/2015 10:17 PM, Ludovic Courtès wrote:
>> Yeah, two commits would do IMO: one to add python-pbr-0.11, and the
>> other one for the rest.
>>
>> Could you do that? This patch series needs to go in before it
>> accumulates dust.
>
> No, it'd be a bloody pain.
>
>
Alex Kost skribis:
> Ludovic Courtès (2015-10-08 14:46 +0300) wrote:
>
>> Alex Kost skribis:
>>
>>> Ludovic Courtès (2015-10-08 01:10 +0300) wrote:
>>>
>>> [...]
Wouldn’t the explanation in the manual of how to use this be relatively
complex? That’s a good benchmark.
>>>
>>> As I see
On Fri, Oct 9, 2015 at 8:23 AM, Ludovic Courtès wrote:
> "Thompson, David" skribis:
>
>> From 4be0c2bfd2e2e9a03d860cfb2ff92aa66cbfaa70 Mon Sep 17 00:00:00 2001
>> From: David Thompson
>> Date: Thu, 8 Oct 2015 21:23:09 -0400
>> Subject: [PATCH] scripts: environment: Use system* instead of system.
Mark H Weaver skribis:
> Andreas Enge writes:
>
>> Hm, I do not understand your message.
>>
>> On Tue, Oct 06, 2015 at 09:45:35PM +0200, Ludovic Courtès wrote:
>>> The problem in question is this:
>>> ...
>>> Long story short: everything is alright. :-)
>>
>> So is there a problem or not? The f
David Thompson skribis:
> From dc72ee831d6c6b93cf404a7fd1abc4b8fb27b7f2 Mon Sep 17 00:00:00 2001
> From: David Thompson
> Date: Fri, 9 Oct 2015 12:33:40 -0400
> Subject: [PATCH] build: container: Fix call-with-clean-exit.
>
> Before, call-with-clean-exit would *always* return an exit code of 1.
"Thompson, David" skribis:
> On Fri, Oct 9, 2015 at 8:40 AM, Ludovic Courtès wrote:
>> Alex Kost skribis:
>>
>>> I don't know if there is a better workaround for the SDL headers, but
>>> this problem is rather common: there is a workaround in 'abbaye' and a
>>> special patch for 'pingus'.
>>>
>
* gnu/packages/wm.scm (bspwm): New package.
* gnu/packages/xdisorg.scm (sxhkd): New package.
---
gnu/packages/wm.scm | 33 +
gnu/packages/xdisorg.scm | 33 +
2 files changed, 66 insertions(+)
diff --git a/gnu/packages/wm.scm b/g
FYI, this is actually my first patch to Guix. (I just installed Guix two days
ago too.) Hopefully this turns out okay, but in any case let me know how I went.
Also, if you see the IRC (#guix) right now (at time of writing), you can see
some discussion between me and rekado about setting "CC=gcc" f
An oversight on my part that I noticed while doing 'guix environment
--container' testing.
>From dc72ee831d6c6b93cf404a7fd1abc4b8fb27b7f2 Mon Sep 17 00:00:00 2001
From: David Thompson
Date: Fri, 9 Oct 2015 12:33:40 -0400
Subject: [PATCH] build: container: Fix call-with-clean-exit.
Before, call-w
On Fri, Oct 9, 2015 at 8:40 AM, Ludovic Courtès wrote:
> Alex Kost skribis:
>
>> I don't know if there is a better workaround for the SDL headers, but
>> this problem is rather common: there is a workaround in 'abbaye' and a
>> special patch for 'pingus'.
>>
>> The problem is: the source code has
Ludovic Courtès (2015-10-08 14:46 +0300) wrote:
> Alex Kost skribis:
>
>> Ludovic Courtès (2015-10-08 01:10 +0300) wrote:
>>
>> [...]
>>> Wouldn’t the explanation in the manual of how to use this be relatively
>>> complex? That’s a good benchmark.
>>
>> As I see it, it is not complex:
>>
>> «Dow
"Thompson, David" skribis:
> From 4be0c2bfd2e2e9a03d860cfb2ff92aa66cbfaa70 Mon Sep 17 00:00:00 2001
> From: David Thompson
> Date: Thu, 8 Oct 2015 21:23:09 -0400
> Subject: [PATCH] scripts: environment: Use system* instead of system.
>
> This allows for direct program invokation without needing
Skimming on the patches, I only have superficial comments:
Ricardo Wurmus skribis:
> From 22c5a75aae3fec3bef18f2186ba87d6891439006 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus
> Date: Tue, 22 Sep 2015 14:58:16 +0200
> Subject: [PATCH 1/8] gnu: Add python-pexpect.
>
> * gnu/packages/python.sc
Alex Kost skribis:
> I don't know if there is a better workaround for the SDL headers, but
> this problem is rather common: there is a workaround in 'abbaye' and a
> special patch for 'pingus'.
>
> The problem is: the source code has lines like this:
>
> #include
>
> but the headers of all SDL
On Thu, Oct 08, 2015 at 08:47:26PM -0400, Mark H Weaver wrote:
> Note that we successfully cross-compile from i686 to
> mips64el-linux-gnu, so I guess that works.
Oh I see, there was a misunderstanding on my part - I somehow thought that
we were successfully disabling the cross-build from i686 to
Ian Denhardt (2015-10-07 22:15 +0300) wrote:
> What about just having command line (non-emacs) tool? I'm thinking
> something inspired by Archlinux's `makepkg -g`, which downloads the
> sources based on the current build script and outputs something that can
> just be copied into it. I don't feel
Alex Kost skribis:
> From beec892399a21b0436a2b971881e5cc15545bec2 Mon Sep 17 00:00:00 2001
> From: Alex Kost
> Date: Sun, 4 Oct 2015 19:49:24 +0300
> Subject: [PATCH 1/2] gnu: Add physfs.
>
> * gnu/packages/physfs.scm: New file.
> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.
I agree with the
Mathieu Lirzin skribis:
> * guix/build/glib-or-gtk-build-system.scm (wrap-all-programs):
> Factorize it.
[...]
> + (define (env-var var dirs)
> +"Associate an environment variable VAR with a list of directory DIRS."
> +(and (not (null? dirs)) (list var ":" 'prefix dirs)))
s/env-var/
19 matches
Mail list logo
