I don't know enough about packaging to answer your question. I've only dealt with bundling standalone packages myself, in which case the so/dlls were just bundled with it.
As far as bugs and maintenace for something like an Ogg Vorbis decoder, I actually think it would be quite low maintenance. The reason being is that the spec is well defined, and isn't changing. Once all decoding is fully implemented, you won't really have to modify it, since there aren't any new versions coming out or features being added to the Vorbis specification. On Saturday, February 25, 2017 at 10:13:17 PM UTC+9, Paul Everitt wrote: > > Thanks for writing back. I don’t know enough about ffmpeg and > packaging…can it be built into a binary wheel for systems that don’t have > it? > > Yes, I think a pure Python Ogg Vorbis might be enough for Arcade. You’re > right that Arcade’s audio needs are pretty basic. OTOH, it’s a trillion > hours of work for you over the next year, not just completing but the (like > avbin) pile of annoying bugs. if I did a bounty, I’d have to get some more > folks putting money in. Still, that’s the most attractive option. > > —Paul > > On Feb 25, 2017, at 3:15 AM, Benjamin Moran <[email protected] > <javascript:>> wrote: > > Hey Paul, > > I know that library. I've maybe chatted with you (or the other > contributors) on Reddit in the past. It's a nice project. > > The avbin issue has been the elephant in the room for a while now. No one > is currently maintaining it, and some linux distributions have dropped it > from their repos. Today, there is a large number of avbin related bugs on > the issue tracker, so it's definitely causing trouble for users. To me, > just writing bindings for ffmpeg seems like the most logical solution. > > Speaking of just audio, I've been working on a pure-python Ogg Vorbis > decoder. I've made a lot of progress so far, but this is one of those > projects that might never be completed. It's pretty mathimatically > intensive stuff. I think that going forward, having libraries like this in > the ecosystem is the best way. It might be slow today, but the portability > makes it valuable. For pyglet, it would probably be fine if your're doing > StaticSources. > > > On Friday, February 24, 2017 at 10:46:39 PM UTC+9, Paul Everitt wrote: >> >> On a barely-related note...I pitch in with the Arcade project (2d games >> for Python) and keeping avbin packaging working has not been fun. >> >> I personally would throw in some money for a bounty, either to keep >> pyglet+avbin viable, or switch to something more maintained. Arcade >> currently only wants avbin for audio. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "pyglet-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pyglet-users/u1OTO2aYFLo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/pyglet-users. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
