search for: isolation1_md5sum

...,8 @@ set -e +. $srcdir/guestfs-md5.sh + # UML backend doesn't support qcow2 format. supports_qcow2=yes if [ "$(guestfish get-backend)" = "uml" ]; then @@ -31,14 +33,14 @@ fi rm -f isolation1.img isolation2.img isolation3.img guestfish sparse isolation1.img 100M -isolation1_md5sum="$(md5sum isolation1.img | awk '{print $1}')" +isolation1_md5sum="$(do_md5 isolation1.img)" guestfish sparse isolation2.img 100M -isolation2_md5sum="$(md5sum isolation2.img | awk '{print $1}')" +isolation2_md5sum="$(do_md5 isolation2.img)"...

Hi, continuing what started a couple of weeks ago [1], the attached patch series continues the work in making it easier to build and run libguestfs (in fixed appliance mode) on OSes different than Linux. The provided changes should cause no functional changes on Linux. [1] https://www.redhat.com/archives/libguestfs/2014-October/msg00176.html Thanks, -- Pino Pino Toscano (9): build: check

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")

These are my thoughts on adding a test harness to run tests instead of using automake. The aim of this exercise is to allow us to run the full test suite on an installed copy of libguestfs. Another aim is to allow us to work around all the limitations and problems of automake. The first patch makes an observation that since the ./run script sets up $PATH to contain all the directories