unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Simon Streit <simon@netpanic.org>
Cc: 54109-done@debbugs.gnu.org
Subject: bug#54109: Document package variable in virtlogd service
Date: Wed, 23 Feb 2022 12:56:04 +0200	[thread overview]
Message-ID: <YhYSxG6jzPXow1RL@3900XT> (raw)
In-Reply-To: <ygubkyygb08.fsf@netpanic.org>

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]

On Tue, Feb 22, 2022 at 04:46:15PM +0100, Simon Streit wrote:
> Hello!
> 
> I would like to suggest a little extension in the manual.
> 
> I noticed that the package variable for virtlogd service is not
> documented.  It is possible to define the package as (libvirt libvirt)
> for said service.  While it is closely related to libvirt-service-type,
> the package variable may still be independently modified.
> 
> This only became clear after using inferiors in libvirt-service-type for
> some time now.  New Qemu packages would still be pulled in after
> reconfiguring with new checkouts.  Unfortunately Qemu's packages take a
> lot of space, which is why I've pinned it to a fixed version.
> 
> Thus I think this should be included into the manual.
> 

I was going to say that the libvirt variable is already mentioned in the
virtualization page, but that's for the libvirt-service-type, not for
the virtlogd-service-type.

Thanks. Patch pushed!


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-02-23 11:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 15:46 bug#54109: Document package variable in virtlogd service Simon Streit
2022-02-23 10:56 ` Efraim Flashner [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=YhYSxG6jzPXow1RL@3900XT \
    --to=efraim@flashner.co.il \
    --cc=54109-done@debbugs.gnu.org \
    --cc=simon@netpanic.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.
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).