From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/6] docs: convert manpages to pod
Date: Mon, 24 Jul 2017 18:09:16 +0200 [thread overview]
Message-ID: <20170724160916.GB8603@aepfle.de> (raw)
In-Reply-To: <22902.6431.562992.752359@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]
On Mon, Jul 24, Ian Jackson wrote:
> Olaf Hering writes ("[PATCH 0/6] docs: convert manpages to pod"):
> > To remove the buildtime dependency to pandoc/ghc some manpages are
> > converted from markdown to pod format. This will provide more manpages
> > which are referenced in xl(1) and xl.cfg(5).
>
> Sorry to ask this at this stage, but: did I miss some discussion of
> why this was desirable ?
Likely yes: https://build.opensuse.org/request/show/511948
The point is: if all manpages need to be build then Xen needs to depend
on pandoc, which in turn depends on ghc. Neither of them is seen as a
"core" package, while "Xen" is a core package. Either ghc becomes a core
package, or Xen is moved out of core. In this context "core" means it is
part of a install DVD, if I understand the concept of "rings" correctly.
Do you see any downside of this series? There is currently a mix of pod
and markdown format for the manpages. This change gets it closer to have
them all as pod.
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-24 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:14 [PATCH 0/6] docs: convert manpages to pod Olaf Hering
2017-07-24 14:14 ` [PATCH 1/6] docs: add pod variant of xen-pv-channel.7 Olaf Hering
2017-07-24 14:14 ` [PATCH 2/6] docs: add pod variant of xl-network-configuration.5 Olaf Hering
2017-07-24 14:14 ` [PATCH 3/6] docs: add pod variant of xl-numa-placement Olaf Hering
2017-07-24 14:14 ` [PATCH 4/6] docs: remove markdown variant of xen-pv-channel.7 Olaf Hering
2017-07-24 14:14 ` [PATCH 5/6] docs: remove markdown variant of xl-network-configuration.5 Olaf Hering
2017-07-24 14:14 ` [PATCH 6/6] docs: remove markdown variant of xl-numa-placement.7 Olaf Hering
2017-07-24 15:58 ` [PATCH 0/6] docs: convert manpages to pod Ian Jackson
2017-07-24 16:09 ` Olaf Hering [this message]
2017-07-24 16:25 ` Ian Jackson
2017-07-24 17:44 ` Olaf Hering
2017-07-25 9:44 ` Ian Jackson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170724160916.GB8603@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.