Hi Ron,
On Wed, 16 Nov 2016 09:23:16 +1030 Ron wrote:
> On Tue, Nov 15, 2016 at 11:16:41PM +0100, Andrey Gursky wrote:
> > Ron,
> >
> > > This is done now. Thanks for your patience.
> >
> > thanks! The 1.2.2 release hasn't been yet officially published by
> > upstream (only tagged in git), but it is already available in Debian!
> >
> > Now looking forward for modernizing the package, so that
> > - arch dependent libs move to /usr/lib/{x86_64-linux-gnu,i386-linux-gnu,..}/
> > lib package becomes:
> > Multi-Arch: same
> > - libao-common becomes
> > Architecture: all
> >
> > Is the issue with plugins the only problem in [1]? libao-common has no
> > binaries, thus it can be already fixed?
> >
> > Regards,
> > Andrey
> >
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638741
>
> Yeah, I haven't forgotten about that one, but there's enough changed in
> this one that I wanted to give it a chance for anything new to shake out
> before messing around with relocating things.
>
> What's your actual use case for needing this one to be m-a?
>
> The zsnes case wasn't terribly compelling, but I am curious about why
> other people might want to use this one cross arch.
Honestly, I don't need libao at the moment. And that's the point. Once
I'd need it, it would be too late to start fixing issues, since only a
reliably working solution would be expected. M-A is a great Debian
achievement and if I notice a packet, that is still not m-a aware, I
kindly ping the maintainer.
I'm wondering, how the plugins are opened by libao: by absolute path or
relying on path has been added for ldconfig? Both seems to be fixable.
Or libao has a long history, which leads to more complex things?
In the hope that Debian will become fully m-a,
Andrey
P.S. The most common case for me is to cross-compile for armhf on amd64.
