On Friday, 13 November 2015 01:22:33 UTC, Benjamin Moran wrote: > > I would guess that the built-in png and wav support is probably adequate > for most users. > > This topic does bear discussion though, because avbin isn't even > available is some Linux distribution repositories. On Arch, for example, it > must be built from the AUR. This wouldn't matter if it was redistributable > without worry, but it seems that it's ambiguous. >
I don't think it had to be ambiguous. I firmly believe that AVbin and and it's source could be distributed with pyglet, if desired that is. We can better a better answer than this though, by a either asking FSF directly (although there website does state its ok already(http://www.gnu.org/licenses/license-list.html#ModifiedBSD) and/or by approaching other projects that do the same, of which there must be many. This assumes pyglet is all under the 3-clases BSD, which is seems may be so according to the FSF: http://directory.fsf.org/wiki/Pyglet#tab=Details > I like the idea of separate dependencies for each codec as you've listed. > I guess it all comes down to maintaining it. > Yes, but AVbin has to me maintained now anyway.It depedens if users/want use the features of ffmpeg/avlib. There are libogg, vorbis etc as I have pointed out that suppor richer formats, and they are 3 clause BSD too. -- 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 http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
