[arch-dev-public] migrate libusb1 to libusb and add libusb-compat to [core]
Hi guys, according to the last post of Allan, it would make much sense to move in libusb-compat to [core] and change the libusb 0.x to libusb 1.x The old apps need to be rebuilt against libusb-compat. In [core] udev still needs the compat layer. any objections? greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Hi guys, according to the last post of Allan, it would make much sense to move in libusb-compat to [core] and change the libusb 0.x to libusb 1.x
The old apps need to be rebuilt against libusb-compat. In [core] udev still needs the compat layer.
any objections? greetings tpowa Ok talked to allan on irc, I move in the things to [staging], greetings tpowa
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Hi guys, according to the last post of Allan, it would make much sense to move in libusb-compat to [core] and change the libusb 0.x to libusb 1.x
The old apps need to be rebuilt against libusb-compat. In [core] udev still needs the compat layer.
any objections? greetings tpowa
Ok talked to allan on irc, I move in the things to [staging], greetings tpowa Todolist created here: http://www.archlinux.org/todo/50/
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 11/28/2010 05:36 PM, Tobias Powalowski wrote:
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Hi guys, according to the last post of Allan, it would make much sense to move in libusb-compat to [core] and change the libusb 0.x to libusb 1.x
The old apps need to be rebuilt against libusb-compat. In [core] udev still needs the compat layer.
any objections? greetings tpowa
Ok talked to allan on irc, I move in the things to [staging], greetings tpowa Todolist created here: http://www.archlinux.org/todo/50/
still don't get it what we have to do. we have a libusb1 in our repo which now libusb is using it . what are we doing with it? -- Ionuț
On 11/28/2010 06:10 PM, Ionuț Bîru wrote:
On 11/28/2010 05:36 PM, Tobias Powalowski wrote:
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Am Sonntag 28 November 2010 schrieb Tobias Powalowski:
Hi guys, according to the last post of Allan, it would make much sense to move in libusb-compat to [core] and change the libusb 0.x to libusb 1.x
The old apps need to be rebuilt against libusb-compat. In [core] udev still needs the compat layer.
any objections? greetings tpowa
Ok talked to allan on irc, I move in the things to [staging], greetings tpowa Todolist created here: http://www.archlinux.org/todo/50/
still don't get it what we have to do. we have a libusb1 in our repo which now libusb is using it . what are we doing with it?
maybe i wasn't clear enough. libusb only replaces libusb1 but the packages that now depends on it are not in todo list and it would break the dependencies chain. -- Ionuț
Am Sonntag 28 November 2010 schrieb Ionuț Bîru: > On 11/28/2010 05:36 PM, Tobias Powalowski wrote: > > Am Sonntag 28 November 2010 schrieb Tobias Powalowski: > >> Am Sonntag 28 November 2010 schrieb Tobias Powalowski: > >>> Hi guys, > >>> according to the last post of Allan, it would make much sense to move > >>> in libusb-compat to [core] and change the libusb 0.x to libusb 1.x > >>> encies (1) > >>> The old apps need to be rebuilt against libusb-compat. > >>> In [core] udev still needs the compat layer. > >>> > >>> any objections? > >>> greetings > >>> tpowa > >> > >> Ok talked to allan on irc, I move in the things to [staging], > >> greetings > >> tpowa > > > > Todolist created here: > > http://www.archlinux.org/todo/50/ > > still don't get it what we have to do. we have a libusb1 in our repo > which now libusb is using it . what are we doing with it? - libusb1 is the successor of libusb 0.1.x - Jan moved this lib into extra in order to allow to build packages wich need libusb 1.x - Now some programs still need libusb 0.1.x functions. The upstream developers created a wrapper for this called libusb-compat The plan is to replace the old unmaintained libusb 0.1.x with the new maintained one. The libusb1 package will die and will be replaced by the libusb package which moves to 1.x series. A new package libusb-compat will be created which support old programs that are not yet libusb 1.x ready. All packages which still need the old functions should be rebuilt against libusb-compat. Hope this clears some things. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Sun, 2010-11-28 at 17:16 +0100, Tobias Powalowski wrote:
- libusb1 is the successor of libusb 0.1.x - Jan moved this lib into extra in order to allow to build packages wich need libusb 1.x - Now some programs still need libusb 0.1.x functions. The upstream developers created a wrapper for this called libusb-compat
The plan is to replace the old unmaintained libusb 0.1.x with the new maintained one.
The libusb1 package will die and will be replaced by the libusb package which moves to 1.x series.
A new package libusb-compat will be created which support old programs that are not yet libusb 1.x ready. All packages which still need the old functions should be rebuilt against libusb-compat.
Hope this clears some things. greetings tpowa
Life would be so much easier if we wouldn't mess so much. Why didn't we choose for the easy solution? libusb1 (extra) -> libusb1 (core). No rebuilds required libusb (core) -> libusb-compat (core). Some replaces/provides/conflicts and we're done.
On 29/11/10 18:25, Jan de Groot wrote:
On Sun, 2010-11-28 at 17:16 +0100, Tobias Powalowski wrote:
- libusb1 is the successor of libusb 0.1.x - Jan moved this lib into extra in order to allow to build packages wich need libusb 1.x - Now some programs still need libusb 0.1.x functions. The upstream developers created a wrapper for this called libusb-compat
The plan is to replace the old unmaintained libusb 0.1.x with the new maintained one.
The libusb1 package will die and will be replaced by the libusb package which moves to 1.x series.
A new package libusb-compat will be created which support old programs that are not yet libusb 1.x ready. All packages which still need the old functions should be rebuilt against libusb-compat.
Hope this clears some things. greetings tpowa
Life would be so much easier if we wouldn't mess so much. Why didn't we choose for the easy solution?
libusb1 (extra) -> libusb1 (core). No rebuilds required libusb (core) -> libusb-compat (core). Some replaces/provides/conflicts and we're done.
Because libusb1 is an ugly package name compared to libusb... We do not tend to add version numbers in package names for other libraries and the rebuild is fairly minimal. Allan
The rebuild is complete and moved to [testing]/[community-testing]. Note that some packages in the TODO list were excessive as the dependency update was handled further down the dependency chain. So do not be concerned if a package you though needed rebuilt is not there... unless of course it should really have been there, in which case file a bug! I'll leave the signoff email to Tobias P given he did the builds for [core]. Allan
participants (4)
-
Allan McRae
-
Ionuț Bîru
-
Jan de Groot
-
Tobias Powalowski