Re: [PATCH] Add fxtract.

On 12/01/16 07:00, Ludovic Courtès wrote: Ben Woodcroft skribis: From acd310d27c457139d3f2fcd2cfc1127167bf2c48 Mon Sep 17 00:00:00 2001 From: Ben Woodcroft Date: Thu, 7 Jan 2016 07:44:58 +1000 Subject: [PATCH] gnu: Add fxtract. *

Re: [PATCH] gnu: boost: Update to 1.60.0

Andreas Enge skribis: > On Wed, Jan 06, 2016 at 11:18:19PM +0100, Ludovic Courtès wrote: >> It has 140 dependent packages, including LibreOffice, so kinda >> borderline for master. It’s probably safer on a separate branch that >> Hydra will build. Mark? > > Finally hydra

Re: Texlive work

Andreas Enge skribis: >(modify-phases %standard-phases > (add-after 'install 'postint >(lambda* (#:key inputs outputs #:allow-other-keys #:rest args) Certified as valid indentation! > (modify-phases > (map (cut assq <>

Re: [PATCH] gnu: boost: Update to 1.60.0

On Mon, Jan 11, 2016 at 10:17:32AM +0100, Ludovic Courtès wrote: > 3. Hope that Debian has a patch to fix this and apply it. Debian is still at 1.58, so this is not an option right now. Andreas

Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.

On Mon, Jan 11, 2016 at 12:14 AM, Mathieu Lirzin wrote: > Hi, > > Federico Beffa writes: > >> HTML is not better than Info. Here we only need to keep it for >> 'emacs-mit-scheme-doc' to work. This is functionality for mit-scheme >> whereby Emacs looks up the

Re: [PATCH 0/2] Add eSpeak

On Tue, Jan 12, 2016 at 12:26:37AM -0500, Leo Famulari wrote: > These patches provide the eSpeak software speech synthesizer [0]. I realized that the espeak upstream has gone inactive [0] and the users have forked the project as espeak-ng: https://github.com/espeak-ng/espeak-ng/ The impression I

Re: New CLI syntax for package version

Ludovic Courtès writes: > In , we came to the conclusion that we need a > new syntax to denote a specific package version on the command line. > > The current syntax is described in the manual (info "(guix) Invoking > guix package"). Basically,

Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.

On Mon, Jan 11, 2016 at 8:06 PM, Leo Famulari wrote: >> It seems you don't get that my point is not about personal preferences >> or feelings. It's about physical impairments (and there are plenty of >> shades of grays between good sight and completely blind, where big, >>

[PATCH 2/2] gnu: Add espeak.

* gnu/packages/audio.scm (espeak): New variable. --- gnu/packages/audio.scm | 52 ++ 1 file changed, 52 insertions(+) diff --git a/gnu/packages/audio.scm b/gnu/packages/audio.scm index 111a82d..2f679b7 100644 --- a/gnu/packages/audio.scm +++

[PATCH 1/2] gnu: Add sonic.

* gnu/packages/audio.scm (sonic): New variable. --- gnu/packages/audio.scm | 34 ++ 1 file changed, 34 insertions(+) diff --git a/gnu/packages/audio.scm b/gnu/packages/audio.scm index ebae5d5..111a82d 100644 --- a/gnu/packages/audio.scm +++

Re: [PATCH] build: Speed up .go compilation.

taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > Well, my observation while testing guix pull was that before, one would > get several Guile processes each taking up about 100 MB memory if I > remember correctly. (As many processes as one has cores.) So for dual- > or

Re: [PATCH] build: Speed up .go compilation.

Mathieu Lirzin skribis: # Unset 'GUILE_LOAD_COMPILED_PATH' altogether while compiling. Otherwise, if # $GUILE_LOAD_COMPILED_PATH contains $(moduledir), we may find .go files in # there that are newer than the local .scm files (for instance because the

Re: [PATCH] Add fxtract.

Ben Woodcroft skribis: > From acd310d27c457139d3f2fcd2cfc1127167bf2c48 Mon Sep 17 00:00:00 2001 > From: Ben Woodcroft > Date: Thu, 7 Jan 2016 07:44:58 +1000 > Subject: [PATCH] gnu: Add fxtract. > > * gnu/packages/bioinformatics.scm (fxtract): New

Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.

Federico Beffa skribis: > On Mon, Jan 11, 2016 at 10:09 AM, Ludovic Courtès wrote: >> Federico Beffa skribis: >> >>> For PDFs, it depends on the type and quality of the manual. If it is >>> short and/or poor, then nobody will spend hours reading

Re: New CLI syntax for package version

shak...@openmailbox.org skribis: > The problem I see with 3. is that the mailing list archives will detect the > package names (with versions, ie the whole strings like ‘guile@1.8’) as email > addresses, and hide them, by replacing them with ‘address@hidden’. As an > example, here’s the mail I

Re: [PATCH] Update Ruby to 2.3.0

On 11/01/16 07:14, Ludovic Courtès wrote: Ben Woodcroft skribis: From 2f26295b5a163cfc5d37332a501dcba5c40fb956 Mon Sep 17 00:00:00 2001 From: Ben Woodcroft Date: Mon, 4 Jan 2016 09:38:42 +1000 Subject: [PATCH 5/5] gnu: ruby: Update to 2.3.0.

Re: New CLI syntax for package version

Hi! […] >>>1. slash, >>> >>> guile:1.8/doc >>> xterm-256-color:320 >>> emacs:24.5/out >>> >>>2. underscore, 9#28> >>> >>> emacs_24.5:out >>> >>>3.

[PATCH] bristol: Try to fix build on ARM + MIPS.

>From 5290edcfa5f7ae8f6363df63b7f0738a7d0de5ac Mon Sep 17 00:00:00 2001 From: Ricardo Wurmus Date: Mon, 11 Jan 2016 19:38:11 +0100 Subject: [PATCH] gnu: bristol: Remove SSE flags on platforms other than x86_64 and i686. * gnu/packages/music.scm (bristol)[arguments]: Add

[PATCHES] Add docker-compose and missing prerequisites.

Hello Guix hackers, As much as I dislike it, the company I work for has started to use Docker. Docker Compose is a special Python program that talks to the Docker daemon to run many containers at once using configuration from a "declarative" YAML file (my kingdom for an sexp), and I didn't want

[PATCH] Build C++ cross-compiler by default.

Hi Guix, the configure flags defined in “cross-gcc-arguments” disabled the C++ compiler to prevent an error that happens when building libstdc++-v3. Since I needed a C++ cross-compiler for ARM I added “c++” to the list of enabled languages and added the configure flag “--disable-libstdc++-v3”.

Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.

On Mon, Jan 11, 2016 at 12:58:41PM +0100, Federico Beffa wrote: > On Mon, Jan 11, 2016 at 10:09 AM, Ludovic Courtès wrote: > > Federico Beffa skribis: > > > >> For PDFs, it depends on the type and quality of the manual. If it is > >> short and/or poor, then nobody

qemu instructions for manual

Hi everyone, I recently started using GuixSD in a virtual machine in advance of getting some dedicated hardware. This process is not well-documented, at least for somebody who is new to QEMU. I don't think our manual should explain how to use QEMU, but I do think it should provide the necessary