2012/9/25 Hans de Goede <hdego...@redhat.com>: > On 09/25/2012 01:41 AM, Pete Batard wrote: >> OK, since I'd like to use the 1.1 version change as an opportunity to slide >> in a couple more API changes (set transfer codes to negative, as well as >> #21, and possibly libusb_strerror), but I doubt people will want to wait a >> week or so, we might as well try to go with a 1.0.14 that reverts bMaxPower. > > Thanks! I believe that reverting the bMaxPower change and doing a 1.0.14 > quickly > is the right decision. I now realize making the bMaxPower change in a stable > API/ABI series clearly was a mistake, and one I'm just as responsible for > as you, since I acked that change!
+1 >> This will occur without RC, > > Ack. Ack > > and, unless somebody else but me wants to take on themselves to maintain a > 1.0.x branch, may be the very last release of the 1.0 branch. > > Here I disagree with you (as you probably expected). I can understand the > desire > to fix various API issues, and to get rid of having to be compatible with the > original libusb, but a soname change, even if done in a way that the result is > parallel installable comes at a large price, not for us as libusbx developers, > but for our users. I agree with Hans. The libusb API is used by "many" projects, at least on GNU/Linux. $ build-rdeps libusb-1.0-0-dev Reverse Build-depends in main: ------------------------------ altos aranym ccid colord cups cutesdr dfu-util eegdev gammu gnuradio gpsd hplip ifpgui libdc1394-22 libfprint libfreenect libgpod libgusb libimobiledevice libmtp libsigrok madwimax mrpt mustang-plug ocaml-usb pcsc-cyberjack psychtoolbox-3 qthid-fcd-controller robocut spice-gtk uhd upower usbmuxd usbredir usbutils xboxdrv Found a total of 37 reverse build-depend(s) for libusb-1.0-0-dev. 37 Debian packages are using libusb-1.0-0-dev as a build dependency. I guess not all of them will be impacted by the bMaxPower change. > Looking at the list for 1.1, although they are all nice to have, none > of them to me is worth the cost of an ABI/API break. So I would really like > to stay us with 1.0.x for now, until we do a 2.0. I know you (Pete) really > want to move forward with all this stuff. So I suggest to create a 1.0.x > branch after the 1.0.14 release, which I will maintain (*), and then you have > your hands free to start working towards a 2.0 release on git master. I also agree. Please wait until version 2.0 to introduce the "minor"/non fundamental API changes. Bye -- Dr. Ludovic Rousseau ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
