On Wed, 22 May 2013, Richard Shaw wrote: > On Wed, May 22, 2013 at 3:56 PM, David Rowe <[email protected]> wrote: > >> I recommend we include the sox source files we need in our source >> repository. Relying on the system sox lib whose internal implementation >> will vary over time and different machines is too risky. >> > > We'll need to be careful though. From a Fedora (and probably Debian) > packaging perspective, copying the files is still considered bundling the > library. If what we need is indeed pretty small, perhaps we could use the > sox code as a template and "re-implement" it and make it native to FreeDV. > Dunno, just a thought.
Ask the SOX project if you can include bits of their code directly. We did that with 3 or 4 libraries in Xastir, and asked them to re-license their sources (in GPL2 for our purposes) in one or two cases. Ask nicely and you might be pleasantly surprised. The developers have the freedom to release their own code under multiple licenses. By including bits of it in your code you lose connection with bug-fixes in the upline library, but if it's a relatively stable library then you're not out much. If both the library and the code you're developing are the same open-source license, you don't even need to ask prior to copying their code. It's probably considered good form to anyway though, so they know where else their code is being applied. -- Curt, WE7U. http://wetnet.net/~we7u APRS Wiki: http://info.aprs.net/ ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
