From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Andy Wingo <wingo@pobox.com>, guix-devel@gnu.org
Subject: Re: elogind WIP
Date: Mon, 04 May 2015 17:07:26 +0200 [thread overview]
Message-ID: <87h9rss7o1.fsf@gnu.org> (raw)
In-Reply-To: <87d22gygvh.fsf@mango.localdomain> (Ricardo Wurmus's message of "Mon, 04 May 2015 08:52:02 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Attached is a patch for a package definition for elogind. I committed a
> couple of changes to my fork of the elogind repository, that had the
> effect of bypassing all build problems.
>
> Actually, that's not quite true. I disabled PAM support, because I
> couldn't get it to work. The symbol "__start_BUS_ERROR_MAP" cannot be
> found at link time. "BUS_ERROR_MAP" apparently is created manually in
> "./src/libelogind/sd-bus/bus-error.h", but this doesn't seem to work
> right.
>
> I have not tested any of the binaries, obviously, so I don't know if
> this is an actually working elogind daemon.
OK. This seems like a good step forward.
> From 645e0c19317ac12286b7c37f086318cb98fcb232 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun, 26 Apr 2015 15:55:59 +0200
> Subject: [PATCH] WIP: add elogind
>
> ---
> gnu/packages/freedesktop.scm | 77 ++++++++++++++++++++++++++++++++++++++++++--
Feel free to commit it (with a proper commit log.)
Then Someone™ should write a service for it and see what this allows us
to run on the GNOME side. Any takers?
Thanks,
Ludo’.
prev parent reply other threads:[~2015-05-04 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 8:40 elogind WIP Andy Wingo
2015-04-23 21:08 ` Ludovic Courtès
2015-04-23 21:11 ` Ludovic Courtès
2015-04-24 21:09 ` Ricardo Wurmus
2015-04-29 20:10 ` Ludovic Courtès
2015-04-29 20:19 ` Ricardo Wurmus
2015-05-04 6:52 ` Ricardo Wurmus
2015-05-04 15:07 ` Ludovic Courtès [this message]
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=87h9rss7o1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=wingo@pobox.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).