On 4/21/12 07:36, "Jose Pablo" <josepablo.cas...@gmail.com> wrote: > >Its like you guys are forcing me to take a side.
In a way yes. > >Where is my freedom to choose if you are forcing me to choose?. Some freedoms are inherently in conflict with other freedoms. >Thats not good for an free and open source software. Thats what open source is. But read on. > > >I explain my self. If I installed software A, and this software uses >libusb-1.0, and I happy with it. >Then I NEED to install software B, and this software uses libusbx-1.0. >Do I have to uninstall software A, even when I NEED it too?? I don't think you understood what libusbx 1.x is and why it exists. It is a meant to be a drop-in-replacement for libusb 1.x so there should be no need to uninstall software A and thats why it NEEDS TO have the same file names. So if it works as advertised, what is the a problem? In the future (libusbx 2.x) when,not if, libusbx will differ from libusb things (including filenames) may/will be different. On the otherhand it seems both inevitable and logical that in that future a compatibility layer will be created for applications that require 1.x functionality/compatibility IF (or when) maintenance of 1.x generation is dropped. libusbx was created with great reluctance because libusb was not going anywhere and many people felt it had no future. Besides I'm sure regardless of your platform there are ways to use libraries with conflicting filenames in most situations. br Kusti ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel