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: Wed, 29 Apr 2015 22:10:17 +0200 [thread overview]
Message-ID: <871tj2hf12.fsf@gnu.org> (raw)
In-Reply-To: <87vbglz11d.fsf@mango.localdomain> (Ricardo Wurmus's message of "Fri, 24 Apr 2015 23:09:18 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> I restored a few files needed to produce man page, renamed two instances
> of "systemd.version", and disabled DTD validation. There are,
> unfortunately, even more XML files that are missing, but they look like
> we shouldn't want them to be part of elogind:
>
> XSLT man/sd-login.html
> warning: failed to load external entity "man/libsystemd-pkgconfig.xml"
> man/sd-login.xml:118: element include: XInclude error : could not load man/libsystemd-pkgconfig.xml, and no fallback was found
> Makefile:4988: recipe for target 'man/sd-login.html' failed
> make[2]: *** [man/sd-login.html] Error 6
sd-login.html sounds like it may have something to do with the logind
part of systemd, no?
> What to do with these files? Should we ignore the man page generation
> for now and rewrite the wee bit we need for elogind? (Or should elogind
> stay close to systemd upstream to make it easier to track development?)
I guess we should stay close to upstream. Nevertheless, we should skip
manual page generation for now if that’s too much of a hindrance, so we
can get started with the more interesting parts. WDYT?
Thanks for looking into it!
Ludo’.
next prev parent reply other threads:[~2015-04-29 20:10 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 [this message]
2015-04-29 20:19 ` Ricardo Wurmus
2015-05-04 6:52 ` Ricardo Wurmus
2015-05-04 15:07 ` 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=871tj2hf12.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).