Re: New ‘--list-generations’ and ‘--delete-generations’ options

2013-09-04 Thread Nikita Karetnikov
The attached procedure will be invoked when either option is called with an argument. It returns an empty list if the argument is not valid. Or when the needed generation can’t be found. Do you see any problems? Please check everything (especially the ‘first-month’ and ‘last-month’ functions).

Naming scheme for Python packages

2013-09-04 Thread Ludovic Courtès
Andreas Enge skribis: > commit 89114f39e4be7ac655fbdd7f00a5f985c8f4ce6b > Author: Andreas Enge > Date: Wed Sep 4 22:12:33 2013 +0200 > > gnu: python: Implement the python naming scheme for pytz and babel. > > * gnu/packages/python.scm (pytz): Rename this ... > * gnu/packages/p

Re: Naming scheme for Python packages

2013-09-04 Thread Andreas Enge
On Wed, Sep 04, 2013 at 10:51:17PM +0200, Ludovic Courtès wrote: > However, I don’t think that scheme should be followed for variable > names: it’s tedious to type, and Guile offers mechanisms to > select/rename bindings imported from other bindings. > Thus I would do: > (define pytz > (packa

Re: Naming scheme for Python packages

2013-09-04 Thread Andreas Enge
On Wed, Sep 04, 2013 at 11:07:44PM +0200, Cyril Roelandt wrote: > And what should we call python2-pytz ? The pytz module compiled with python-2 and installed into lib/python2.7/site-packages/, as opposed to the same module compiled with the default python-3. Compare python-unidecode and python3-un

Re: Naming scheme for Python packages

2013-09-04 Thread Andreas Enge
Apparently, I am getting tired. Especially the variable names must be distinct: There is python-pytz (as a module for python=python-3) and python2-pytz (as a module for python-2) inside the same scheme module. Unless we wish to create scheme modules python2 and python3, which I find rather awkward

Re: Naming scheme for Python packages

2013-09-04 Thread Cyril Roelandt
On 09/04/2013 10:51 PM, Ludovic Courtès wrote: Thus I would do: (define pytz (package (name "python-pytz") ...)) And what should we call python2-pytz ? Cyril.

Re: Naming scheme for Python packages

2013-09-04 Thread Andreas Enge
On Wed, Sep 04, 2013 at 10:52:08PM +0200, Cyril Roelandt wrote: > (define pytz > (package > (name "python-pytz") > ...)) > This is quite Debianish. I like it. But the alternative (as I suggested in the packaging guidelines) is as debianish: > (define python-pytz > (packag

Re: Naming scheme for Python packages

2013-09-04 Thread Cyril Roelandt
On 09/04/2013 10:51 PM, Ludovic Courtès wrote: Andreas Enge skribis: commit 89114f39e4be7ac655fbdd7f00a5f985c8f4ce6b Author: Andreas Enge Date: Wed Sep 4 22:12:33 2013 +0200 gnu: python: Implement the python naming scheme for pytz and babel. * gnu/packages/python.scm (pytz): Ren

Re: [PATCH] gnu: Add itstool.

2013-09-04 Thread Ludovic Courtès
Cyril Roelandt skribis: > * gnu/packages/glib.scm (itstool): New variable. I agree with Nikita’s comments, but otherwise fine with me! Ludo’.

Re: [PATCH] gnu: Add itstool.

2013-09-04 Thread Nikita Karetnikov
> + (uri (string-append "http://files.itstool.org/itstool/itstool-"; > + version ".tar.bz2")) The above should look like this: (uri (string-append "http://files.itstool.org/itstool/itstool-"; version ".tar.bz2")) > +each message to be translated

[PATCH] gnu: Add itstool.

2013-09-04 Thread Cyril Roelandt
* gnu/packages/glib.scm (itstool): New variable. --- gnu/packages/glib.scm | 34 ++ 1 file changed, 34 insertions(+) diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm index 63751bb..eb0dc91 100644 --- a/gnu/packages/glib.scm +++ b/gnu/packages/glib.scm @

Re: MIPS64/N64 support

2013-09-04 Thread Ludovic Courtès
Nikita Karetnikov skribis: >> If you can cross-compile (really: substitute) them from x86_64, the >> better (you can even log in to hydra.gnu.org and get them from there.) >> Otherwise let me know and we’ll arrange something. > > $ ./pre-inst-env guix build binutils-static-stripped-tarball \ >