On 4/21/12 08:58, "Jose Pablo" <josepablo.cas...@gmail.com> wrote:
>I understand that NOW its not a problem. But in a future may be a >problem. So, why don' t change the names NOW and prevent future problems? At the moment the priority is to the project of the ground and get as many people as possible onboard. The purpose of 1.0.x release is to let USERs enjoy the benefits of two years of accumulated improvements, patches, bug fixes and last but not least finally get an official release of for the Windows backend. To this end using the old filenames seems like the best option. I can only speak for myself but I do not see it likely that libusbx 1.x (or libusb for that matter) will go out of its way to break neither the ABI or API in the future. So there is no compelling reason in sight to use both libraries unless your application depends on specific version of the library at which point you have to use whatever mechanism your platform/circumstance provides/ dictates to solve that issue. (As a side note and mostly commercial software developer actually responsible for making things work, I must say I'm in favor of always bundling , dynamically or staticaly, your libraries with your application, especially small ones like libusb, that is the only way to ensure compatibility, none of your shared library hell than you. And in that context the whole filename point is moot anyway). As libusbx goes forward, at some point ABI and API breakage will be unavoidable. At that point the file name changes are probably in order, but that does not make is necessary nor sensical to change them now when we aim to, I repeat, drop-in-replacement for libusb. This is the best option for the users IMO, get the bug fixes without minimum of hassle. I say this as user in waiting for more than two years. 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
