[Slackbuilds-users] qemu annotations

[King Beowulf]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/26/2014 10:20 AM, Willy Sudiarto Raharjo wrote:
>> Spiffy.  How about we add a libusb present sanity check in case
>> in case someone what's to skip USB pasthrough and not build a
>> new libusb? For example,
> 
>> https://gitorious.org/kingbeowulf/sbo-slackbuilds/commit/70a11441a757682ae647b29fa8cd25c8de269513
>
>>  I might not have that quite right, so advise as needed.
> 
> if the check is based on source existence, then all users using
> (semi) automated tools, such as sbopkg will surely build USB
> passthrough as it will download all source mentioned in DOWNLOAD or
> DOWNLOAD_x86_64
> 
> 
> -- Willy Sudiarto Raharjo

I wasn't really worrying about the "automagical tools" folks, just a
check for those, like me, that build stuff manually, only to have the
script fail due to a missing tarball.  I've added a note in the README
to provide a reminder, but who reads those?

So the question is,

(1) do we want to enforce the use of the newer static libusb and thus
have the script fail if libusb source is missing or should the script
continue on the assumption that libusb is not needed?

(2) have users upgrade the libusb in 14.1, i.e, libusb-1.0.19-sbo as a
qemu dependency? Are there 14.1 packages dependent on libusb that
upgrading could break?

In the long run, #2 might be better...depending on when -current goes
- -stable. Leaving the SBo script as vanilla as possible will make the
SBo transition easier when we all upgrade.

- -Ed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlSeAaEACgkQXvwMaW61dLdg1ACeOLhM1q7kZp8XWQ1EW5BAKtqu
J0kAoKrsmgSwd8uxHS9vj5ab2xbIPHBF
=TlJF
-----END PGP SIGNATURE-----