-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > 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.
what if we provide a variable check, such as LIBUSB=yes sh ./qemu.SlackBuild will build libusb-0.19 statically, otherwise, it will not be built - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSeA7QACgkQiHuDdNczM4FXzgCeOsgcII+9jd7gqjiVqdWmwWng g4wAn1ddRa1FhinOkvD3NtyRIzfgAiCi =gi/U -----END PGP SIGNATURE----- _______________________________________________ SlackBuilds-users mailing list [email protected] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
