Re: [PATCH] Testbeds for libudev/gudev clients

Lucas De Marchi [2012-07-09 17:21 -0300]:
> > So the trade is "add the get_prefix() calls to the path name build
> > calls" vs. "maintain/build/install a preload library".
> 
> I never ever install that, and doing so is just wrong IMO. Just make
> it part of the "make check". The final user is not supposed to be
> running a testsuite.

This is not (primarily) for testing libudev/gudev itself. The whole
point of this is to make the functionality available to users of
libudev/gudev so that you can write tests for _those_ easily. I
already pointed out two existing examples (upower and
ubuntu-drivers-common) in my initial mail. This is also why I wrote
that entire GUdevTestbed; testing gudev itself would be a lot simpler,
but that's not the reason why we need it.

So we do have to ship it, and document how upower and friends have to
use it (presumably an "udevtestbed" wrapper script which finds and
preloads the test library).

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html