On 2014.01.09 06:30, Bent Bisballe Nyeng wrote: > How much difference will there be to libusbx-1.0.18 and libusb-1.0.18?
As far as developers are concerned, no difference. > What I mean is; will the merge simply be a copy of the current libusbx > code to the libusb repository Yup. Just one extra commit was added, that basically changes a bunch of "libusbx" strings back to "libusb". And since no libusbx string was ever used as part of the API call, outside of LIBUSBX_API_VERSION, for which we have a workaround (#define LIBUSBX_API_VERSION LIBUSB_API_VERSION), you can just drop a library in place of the other, and, as long as it was compiled with the same options, it will work (or fail) in the exact same manner. > or are there still parts of libusb code > left that were otherwise changed in the libusbx project? Nope. The functionality is exactly the same. There's no feature or bugfix in one has the other doesn't replicate exactly. If you check the git repositories for both libraries, this should also be fairly obvious. I'm also going to duplicate part of the libusbx announcement that went to this very list right before the announcement you are replying to, and that tried to explain that the libraries are virtually identical: "As far as the code is concerned, the current libusb repository and the current libusbx repository can be considered identical, and of course the libraries are fully interchangeable, up to the latest libusbx features and bug fixes. The only difference between the library stands in one commit, that updates most of the comments and documentation that was referencing libusbx, into referencing the updated libusb." And just to eliminate any further question you may have on this, we will of course carry any commit applied to one library into the other, up to the 1.0.18 release, in about 2 weeks time, so that the actual releases too are virtually identical. >> o The old .org website is no longer used by the libusb project. >> The main website has now moved to: http://libusb.info > > What are the reasons for abandoning the old .org domain? It's controlled by someone who doesn't like libusbx and with whom we have been unable to reach any form of compromise for many years now (which is the reason there was a libusbx fork in the first place). Now that we have regained control of the SourceForge project, we consider that losing the old domain is an acceptable *temporary* drawback, if it eventually means that developers can access a living and breathing libusb back again. > I think it > should at least contain a forward/link to the new site since a huge > amount of old libusb users who are not reading this list will direct > their browsers directly to libusb.org and thereby never find out about > the new releases. There's nothing we can do about the content of the old .org site. On the other hand, *you* and everybody here, can help make sure that people looking for libusb will find the libusb.info site faster, by helping publicizing that http://libusb.info is the new home of libusb, as well as ceasing to mention the URL for the old site altogether. It's unfortunate that we have to switch domains, but then again, an Open Source project needs not have a domain with a specific extension. As soon as a critical mass of people start referencing the home page that the project indicates, search engines will also reference it, and people will find that page first. Regards, /Pete ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
