From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] doc: fix the configuration path
Date: Thu, 7 Feb 2019 17:31:37 +0100 [thread overview]
Message-ID: <7c5bc3fe-116e-f29c-977d-cac890bdfa93@redhat.com> (raw)
In-Reply-To: <20181126105125.30973-1-marcandre.lureau@redhat.com>
On 11/26/18 11:51 AM, Marc-André Lureau wrote:
> Use a CONFDIR variable to show the configured sysconf path in the
> generated documentations (html, man pages etc).
>
> Related to:
> https://bugzilla.redhat.com/show_bug.cgi?id=1644985
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> Makefile | 9 ++++++---
> qemu-ga.texi | 4 ++--
> 2 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 9cc4dae1a6..a39c231d1c 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -932,11 +932,14 @@ ui/shader.o: $(SRC_PATH)/ui/shader.c \
> MAKEINFO=makeinfo
> MAKEINFOINCLUDES= -I docs -I $(<D) -I $(@D)
> MAKEINFOFLAGS=--no-split --number-sections $(MAKEINFOINCLUDES)
> -TEXI2PODFLAGS=$(MAKEINFOINCLUDES) "-DVERSION=$(VERSION)"
> +TEXI2PODFLAGS=$(MAKEINFOINCLUDES) -DVERSION="$(VERSION)" -DCONFDIR="$(qemu_confdir)"
> TEXI2PDFFLAGS=$(if $(V),,--quiet) -I $(SRC_PATH) $(MAKEINFOINCLUDES)
>
> -docs/version.texi: $(SRC_PATH)/VERSION
> - $(call quiet-command,echo "@set VERSION $(VERSION)" > $@,"GEN","$@")
> +docs/version.texi: $(SRC_PATH)/VERSION config-host.mak
> + $(call quiet-command,(\
> + echo "@set VERSION $(VERSION)" && \
> + echo "@set CONFDIR $(qemu_confdir)" \
> + )> $@,"GEN","$@")
>
> %.html: %.texi docs/version.texi
> $(call quiet-command,LC_ALL=C $(MAKEINFO) $(MAKEINFOFLAGS) --no-headers \
> diff --git a/qemu-ga.texi b/qemu-ga.texi
> index 4c7a8fd163..f00ad830f2 100644
> --- a/qemu-ga.texi
> +++ b/qemu-ga.texi
> @@ -30,7 +30,7 @@ set user's password
> @end itemize
>
> qemu-ga will read a system configuration file on startup (located at
> -@file{/etc/qemu/qemu-ga.conf} by default), then parse remaining
> +@file{@value{CONFDIR}/qemu-ga.conf} by default), then parse remaining
> configuration options on the command line. For the same key, the last
> option wins, but the lists accumulate (see below for configuration
> file format).
> @@ -58,7 +58,7 @@ file format).
> Enable fsfreeze hook. Accepts an optional argument that specifies
> script to run on freeze/thaw. Script will be called with
> 'freeze'/'thaw' arguments accordingly (default is
> - @samp{/etc/qemu/fsfreeze-hook}). If using -F with an argument, do
> + @samp{@value{CONFDIR}/fsfreeze-hook}). If using -F with an argument, do
> not follow -F with a space (for example:
> @samp{-F/var/run/fsfreezehook.sh}).
>
>
next prev parent reply other threads:[~2019-02-07 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 10:51 [Qemu-devel] [PATCH] doc: fix the configuration path Marc-André Lureau
2019-02-07 13:55 ` Marc-André Lureau
2019-02-07 16:31 ` Philippe Mathieu-Daudé [this message]
[not found] ` <1d019621-50b2-1118-a477-e7fffc8147ff@redhat.com>
2019-04-11 19:59 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-04-11 19:59 ` Laurent Vivier
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=7c5bc3fe-116e-f29c-977d-cac890bdfa93@redhat.com \
--to=philmd@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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 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 NNTP newsgroup(s).