On Sat, 9 Jan 2016 01:20:15 +0100 Aurelien Jarno <aure...@debian.org> wrote:
> On 2016-01-09 01:05, Stefan Lippers-Hollmann wrote:
>
> > I'm asking because there are two options:
> >
> > - pushing the current upstream version, with a transition, involving
> > around 30 rdepends, needing sourceful uploads for most of them, and
> > a rather complex device specific config migration, plus some pending
> > packaging work
> >
> > or
> >
> > - backporting (looks to be pretty reasonable) the necessary changes
for
> > libusb 1.0 to lirc 0.9.0 (or 0.9.1, which 'only' needs the config
> > migration, but not the library transition and the corresponding
> > transition slot).
Some time later, the current upstream version is indeed pushed. This
resolves a lot of issues, but not this.
Upstream is still using the 0.1 interfaces. On Fedora, these are
implemented by a compatibility package on top of the modern 1.0 library.
However, I have understood that this is not the Debain Way. That said, I
don't really see the resources upstream which are willing to undertake
the 0.1 -> 1.0 transition. Part of the problem is that here is driver
code which requires specific hardware to test.
That is, is it really, really impossible to use the compatibility
package which actually works on Fedora to resolve this?
--alec
