unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 47285-done@debbugs.gnu.org
Subject: bug#47285: [PATCH 0/4] Update libvirt and friends.
Date: Wed, 31 Mar 2021 15:28:36 +0200	[thread overview]
Message-ID: <87czvfa1vf.fsf@gnu.org> (raw)
In-Reply-To: <87o8fdwmdn.fsf@gmx.com> (Pierre Langlois's message of "Sat, 20 Mar 2021 21:23:00 +0000")

Hi Pierre,

Pierre Langlois <pierre.langlois@gmx.com> skribis:

> This is a patch series that updates libvirt to 7.1.0, now using the
> meson build system, and then updates a few dependent packages as well.
>
> Getting libvirt to build and then work properly was quite tedious, given
> that we have to build it so that the binaries refer to /etc and /var at
> runtime, while we set the prefix to the package output.  This was
> relatively straight-forward with the old build system, but with meson I
> ended up having to patch meson.build so that:
>
>   - It allows for localstatedir to not be relative to the prefix. And
>     prevent it from trying to create empty directories in /var during
>     installation.
>
>   - It allows installing configurations, in /gnu/...-libvirt-7.1.0/etc/,
>     but still refer to the system /etc at runtime.  An alternative would
>     be to not do any of the installation steps for /etc files, but doing
>     that was more intrusive a change to the build system, and having
>     those configurations installed could be useful examples, or referred
>     to be services.
>
> Other than that, the rest is pretty straight-forward.  I've tested this
> using the libvirt service and virt-manager, making sure I could still
> boot a VM.  It's all working fine for me, although my use-case is quite
> simple, just the defaults:
>
> (services (cons*
>             (service libvirt-service-type
>               (libvirt-configuration
>                 (unix-sock-group "libvirt")))
>             ...))
>
> Let me know what you think and if that's good enough to apply!  The
> definition is a bit more hacky than I'd like, so any ideas to improve it
> would be great.

AFAICS it all works like a charm, including the system test :-), so I
went ahead and applied the whole series.

Thank you!

Ludo’.




      parent reply	other threads:[~2021-03-31 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 21:23 [bug#47285] [PATCH 0/4] Update libvirt and friends Pierre Langlois
2021-03-20 21:31 ` [bug#47285] [PATCH 1/4] gnu: libvirt: Update to 7.1.0 Pierre Langlois
2021-03-20 21:31   ` [bug#47285] [PATCH 2/4] gnu: python-libvirt: " Pierre Langlois
2021-03-20 21:31   ` [bug#47285] [PATCH 3/4] gnu: libvirt-glib: Update to 4.0.0 Pierre Langlois
2021-03-20 21:31   ` [bug#47285] [PATCH 4/4] gnu: virt-manager: Update to 3.2.0 Pierre Langlois
2021-03-20 21:32 ` [bug#47285] [PATCH 0/4] Update libvirt and friends Pierre Langlois
2021-03-31 13:28 ` 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=87czvfa1vf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47285-done@debbugs.gnu.org \
    --cc=pierre.langlois@gmx.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).