Re: MIPS64/N64 support

Nikita Karetnikov writes: > OK, I fetched the tarballs. Now I’m getting this error. > > > $ ./pre-inst-env guix build -K hello > > [...] > > make-3.82/main.c > make-3.82/README.OS2 > make-3.82/remote-cstms.c > phase `unpack' succeeded after 4 seconds [...] > pwd: error retrieving current directo

Re: Brasero, or gnome without gnome

Am Mittwoch, den 09.10.2013, 22:22 +0200 schrieb Ludovic Courtès: > I think we can follow our personal preferences to start with (I got > Guile, Emacs, and Ratpoison because that’s pretty much all I > need ;-)). > We do want to support some of these fancy desktops, but I don’t think > there’s much

Re: [PATCH] doc: Add 'copyrights' and 'license' macros.

Nikita Karetnikov skribis: > From b8867a4956af60065200c3b89604108cd7e46e83 Mon Sep 17 00:00:00 2001 > From: Nikita Karetnikov > Date: Wed, 9 Oct 2013 10:37:34 + > Subject: [PATCH] doc: Add 'copyrights' and 'license' macros. > > * doc/guix.texi (YEARS): Remove it. > (copyrights, license): A

Re: [PATCH] doc: Add 'copyrights' and 'license' macros.

And yeah, there could be a single macro since the two always go together. Why is a macro needed at all? (vs. just using text inside @copying).

Re: a2ps: manpages fail to build

Nikita Karetnikov skribis: >> There’s a bug in its build system, but most likely it wants ‘help2man’ >> (as native input.) > > Could you expand on the bug part? It invokes /missing instead of $top_srcdir/build-aux/missing. > I added ‘help2man’, but it didn’t help. Could you check the configure

Re: a2ps: manpages fail to build

> There’s a bug in its build system, but most likely it wants ‘help2man’ > (as native input.) Could you expand on the bug part? I added ‘help2man’, but it didn’t help. > Rather use (substitute* (find-files "." ".*") ...) if that works. It takes too much time, or I’m doing something wrong. > No

Re: Translation of package descriptions and synopses

œôòùd have to make sure Guix can have .po files in the end I believe that is what you'll get with GNUN (the web translators). What I imagine is that you would be getting the .po from www instead of tp, with no other difference in the process. We'll have to talk with Ineiev about the det

Re: [PATCH] doc: Add 'copyrights' and 'license' macros.

What do you think about this change? Sorry, I don't understand what problem you're trying to solve. Why are you separating copyright text and license text? Can you send me the whole file (beginning of it, anyway)? The diff is hard to read. As for the @itemize of names, I would suggest exp

Re: Treating patches as part of ‘origin’

As a bonus, we can now easily show the patches of each package on (commit d4f1ce4). (Go for instance to ‘guile-static-stripped-tarball’ and click on “Expand”.) Ludo’.

Re: a2ps: manpages fail to build

Nikita Karetnikov skribis: > make[2]: Entering directory `/tmp/nix-build-a2ps-4.14.drv-7/a2ps-4.14/man' > Updating man page fixps.1 > Updating man page psmandup.1 > Updating man page card.1 > /nix/store/vw6j6hcbcg2siv93v66d7i3fswyj116k-bash-4.2/bin/bash: line 3: > /missing: No such file or direc

a2ps: manpages fail to build

I’m getting the following error: make[2]: Entering directory `/tmp/nix-build-a2ps-4.14.drv-7/a2ps-4.14/man' Updating man page fixps.1 Updating man page psmandup.1 Updating man page card.1 /nix/store/vw6j6hcbcg2siv93v66d7i3fswyj116k-bash-4.2/bin/bash: line 3: /missing: No such file or directory /n

Re: Brasero, or gnome without gnome

Aljosha Papsch skribis: > Am Montag, den 07.10.2013, 21:53 +0200 schrieb Andreas Enge: >> In any case, I assume one could start by packaging single gnome >> applications, > > The question is which gnome applications. My personal priority list > would be: > > * gnome-terminal > * rhythmbox > * se

Re: Brasero, or gnome without gnome

Am Montag, den 07.10.2013, 21:53 +0200 schrieb Andreas Enge: > In any case, I assume one could start by packaging single gnome > applications, The question is which gnome applications. My personal priority list would be: * gnome-terminal * rhythmbox * seahorse * transmission-gtk * file-roller

Re: Synchronizing descriptions with GSRC?

l...@gnu.org (Ludovic Courtès) skribis: > Brandon Invergo skribis: > Perhaps it would be best to keep all canonical package descriptions, short and long, in a single file under revision control somewhere, such as in womb. They would then be available for anyone who needs them, >>>

Re: Synchronizing descriptions with GSRC?

l...@gnu.org (Ludovic Courtès) writes: > Excellent, thanks! I’ve updated the synchronization tool in Guix to use > this file, and then I’ll update the descriptions (a bit of work for > today, but I’m glad that means less work in the longer term ;-)). > > How complete is this list currently? I se

Re: Synchronizing descriptions with GSRC?

Hi, Brandon! Brandon Invergo skribis: >>> Perhaps it would be best to keep all canonical package descriptions, >>> short and long, in a single file under revision control somewhere, such >>> as in womb. They would then be available for anyone who needs them, >>> should any need arise in the fut

Re: MIPS64/N64 support

Mark H Weaver skribis: > This is the entry that reports the wrong inode number. Note that this > is a bind mount that mirrors /tmp/nix-build-make-boot0-3.82.drv-0 . > > I guess that /tmp/nix-build-make-boot0-3.82.drv-0 should have > the same inode as /tmp/nix-build-make-boot0-3.82.drv-0/. , but

Re: MIPS64/N64 support

Hi Mark, Thanks for the thorough analysis. Mark H Weaver skribis: > My suspicion is that my kernel (linux-libre-2.6.39.1) and Guix's glibc > are not playing nicely together. However, Guix's glibc was configured > to support kernels as early as 2.6.30, and the same 'pwd' executable > that fails

[PATCH] doc: Add 'copyrights' and 'license' macros.

What do you think about this change? I used ‘itemize’ to avoid extraneous blank lines. The only downside is that the indentation of the ‘copyrights’ macro slightly differs from the surrounding text. Karl, do you know a better way? From b8867a4956af60065200c3b89604108cd7e46e83 Mon Sep 17 00:00:0

Translation of package descriptions and synopses

Karl Berry skribis: > Should the transltion be done in Womb? > > I don't think that would be practical. > > These descriptions (in HTML form) will end up on www.gnu.org. Therefore > the web translators (not the TP translators) will be translating them. > I believe po format is involved and