unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: What for 0.5?
Date: Wed, 06 Nov 2013 14:04:10 +0100	[thread overview]
Message-ID: <877gcllm0l.fsf@gnu.org> (raw)
In-Reply-To: <527934B3.2050106@gmail.com> (Cyril Roelandt's message of "Tue, 05 Nov 2013 19:10:59 +0100")

Cyril Roelandt <tipecaml@gmail.com> skribis:

> On 11/03/2013 11:01 PM, Ludovic Courtès wrote:
>>    • More packages, ideally in the GUI/desktop area (you can help! :-)).
>
> Where are we exactly with GNOME ? Last time I checked, I could not use
> evince, nor eog (that I still have to push...). It would be nice to
> find out how to get those to work, so we can truly say we have parts
> of a DE working :p

Exactly, thanks for volunteering!  :-)

For the record, the problem was described at
<https://lists.gnu.org/archive/html/guix-devel/2013-10/msg00028.html>.

The envisioned solutions are:

  • Adding support for “profile hooks”, and use that (may have to wait
    until after 0.5.)

  • Use a hack like that of Nixpkgs, which systematically copies and
    rebuilds (with glib-compile-schemas) the “standard” schemas: see
    ‘doCompileSchemas’ at
    <https://github.com/NixOS/nixpkgs/blob/master/pkgs/desktops/gnome-3/core/gsettings-desktop-schemas/default.nix>
    and its use at
    <https://github.com/NixOS/nixpkgs/blob/master/pkgs/desktops/gnome-3/core/evince/default.nix>.

The latter seems reasonable, and fairly easy to do.

Thoughts?

Ludo’.

  reply	other threads:[~2013-11-06 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 22:01 What for 0.5? Ludovic Courtès
2013-11-05 18:10 ` Cyril Roelandt
2013-11-06 13:04   ` Ludovic Courtès [this message]
2013-11-11 17:50     ` Andreas Enge
2013-11-11 20:35       ` Ludovic Courtès
2013-12-03 21:44 ` Ludovic Courtès
2013-12-09 21:19   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877gcllm0l.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tipecaml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).