I appreciate that merging is incomplete and still requires a lot of work.
But my complaint is that this is highly intransparent, and the result is
confusing to outsiders. Indeed, except for that email I dug out from a mailing
list archive, there is no explicit hint that the libusb and libusbx projects
are going to merge back together, on friendly terms.
However, on http://www.libusb.org/ the download links got replace by links to
libusbx. To an outsider, this leaves a very strange impression. Indeed, my
first (negative) thought was that somebody was hijacking the libusb project, in
bad faith, as has happened in the past in other cases (I named ffmpeg vs. libav
as an example).
So, if you say the merge is so incomplete that you don't want to announce it
anywhere yet, I am all with you, but then I think you should revert those
download links on libusb.org back to libusb, too! Or, if you think that users
really, *really* need to use libusbx, and thus should download libusbx, then at
the very least, insert a short notice before the download links on libusb.org,
something like this:
"The libusb and libusbx projects are going to merge back together [insert
link to email announcing this]. This process will take some time, please be
patient. But already now, we think it is important that libusb users switch to
libusbx, and hence we have updated the download links below to point to
libusbx."
This way, at least one knows what is going on, and in case of bugs and problems
with the code one just downloaded, at least now one knows that this is indeed
libusbx, and not libusb, and one should hence consult a different website, etc.
etc.
The current state, though, seems like a *very* bad idea to me...
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/123#issuecomment-21789151
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
