* gnu/system/shadow.scm (): "shell" field is a string,
and should point to the current profile. This allows pkexec's
dubious check that $SHELL is a valid shell to succeed.
* gnu/services/base.scm (guix-build-accounts):
* gnu/services/networking.scm (bitlbee-service):
* gnu/system.scm (user-acc
* gnu/packages/gnome.scm (gnome-settings-daemon): Use the wacom packages.
---
gnu/packages/gnome.scm | 18 ++
1 file changed, 6 insertions(+), 12 deletions(-)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index e7f854d..92e8e64 100644
--- a/gnu/packages/gnome.scm
++
* gnu/packages/wacom.scm: New file.
* gnu-system.am (GNU_SYSTEM_MODULES): Add wacom.scm.
---
gnu-system.am | 1 +
gnu/packages/wacom.scm | 97 ++
2 files changed, 98 insertions(+)
create mode 100644 gnu/packages/wacom.scm
diff --git a/gnu
* gnu/services/polkit.scm: New file.
* gnu-system.am (GNU_SYSTEM_MODULES): Add polkit service definition.
---
gnu-system.am | 1 +
gnu/services/polkit.scm | 67 +
2 files changed, 68 insertions(+)
create mode 100644 gnu/services/polkit.sc
Andy Wingo writes:
> diff --git a/gnu/packages/wacom.scm b/gnu/packages/wacom.scm
> new file mode 100644
> index 000..76e7b2e
> --- /dev/null
> +++ b/gnu/packages/wacom.scm
> @@ -0,0 +1,97 @@
> +;;; GNU Guix --- Functional package management for GNU
> +;;; Copyright © 2014 Eric Bavier
Is th
Tomáš Čech skribis:
> as project for my Hackweek in SUSE I decided to spend my time on LVM
> support in GuixSD - something I miss greatly. This also means that
> I'll have much less time for that after this week :(
Well this is nice already!
> So far I spent time on reviving my GuixSD installat
>From ca3474b1a639e43d708aad4385057cd84e3cce8b Mon Sep 17 00:00:00 2001
From: Ricardo Wurmus
Date: Wed, 15 Apr 2015 17:46:35 +0200
Subject: [PATCH] gnu: Add Biopython.
* gnu/packages/bioinformatics.scm (python-biopython, python2-biopython): New
variables.
---
gnu/packages/bioinformatics.scm |
Also with the latest release of IcedTea (2.5.5) I get the same linker
error. I obviously do not get this with IcedTea 1.13.x. Here's the
matching section of the build logs for IcedTea 1.13.7 where you see
... nothing bad at all happening:
...
make[6]: Entering directory
'/buildtmp/nix-
Ricardo Wurmus skribis:
> From ca3474b1a639e43d708aad4385057cd84e3cce8b Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus
> Date: Wed, 15 Apr 2015 17:46:35 +0200
> Subject: [PATCH] gnu: Add Biopython.
>
> * gnu/packages/bioinformatics.scm (python-biopython, python2-biopython): New
> variables.
Ricardo Wurmus skribis:
> Note: I did not run the complete test suite again (because it takes a
> very long time on my machine), and when tests are enabled a couple more
> libraries are created. Since they all probably share LIB_LINK_FLAGS I
> expect any problems there to also be fixed by this p
Mark H Weaver skribis:
> I would very much prefer to have just one of ffmpeg/libav in Guix, for
> all the reasons given above against code duplication.
Agreed.
Ludo’.
Ricardo Wurmus skribis:
> "fastx-toolkit" installs three m4 files to "$out/share/aclocal", and
> libgtextutils installs an empty "$out/share/aclocal" directoy. I
> reported this upstream, but I did not add a phase to remove these files,
> because I think it's not a big deal. Is this okay or sho
Mark H Weaver skribis:
> "Jason Self" writes:
>> Also, since Alexandre Oliva periodically removes tarballs so as to
>> free up space on the virtual machine that hosts these, it might also
>> be a good idea to put a copy of linux-libre-3.18.11-gnu.tar.xz in
>> http://alpha.gnu.org/gnu/guix/mirror
Federico Beffa skribis:
> On top of the mentioned cases above, there are many programs making use
> of caches. Some are:
>
> * GLib's IO modules normally use a cache file 'giomodule.cache'. We set
> the env. var. GIO_EXTRA_MODULES, but it's use is explicitly
> discouraged by the project.
>
>
I’ve documented installation from the binary tarball (which I plan to
distribute for the next release) in commit 09722b1. Please let me know
what you think.
Ludo’.
2.1 Binary Installation
===
This section describes how to install Guix on an arbitrary system from a
self-cont
Great :). I would make it a little clearer that this is
'bootstrapping' and hype it a little more that now there is no reason
NOT to install Guix. Only 100Mb on your HDD.
The warning about overwriting a Guix installation should be earlier.
Maybe point out that if you want to move a package with de
On Wed, Apr 15, 2015 at 02:32:14PM +0200, Ludovic Courtès wrote:
Tomáš Čech skribis:
as project for my Hackweek in SUSE I decided to spend my time on LVM
support in GuixSD - something I miss greatly. This also means that
I'll have much less time for that after this week :(
Well this is nice
17 matches
Mail list logo