On Tue, 11 Jun 2013, Richard Shaw wrote:

> While I am both a Fedora packager and the author of the cmake config, I'm
> not really a programmer so I'll have to leave the source tweaking to
> others. :)

I'm both, but it doesn't mean I want to get my hands dirty in the source code 
for yet another project...  I'll contribute if/where I can though.


> As far as sox, that's why I did a static build for freedv. That way you
> don't have to worry about it messing up other repository packages or having
> to rebuild the EL packages against the newer sox.

Roger.  Can that static Sox build be incorporated into the cmake build?  Maybe 
that's an option I missed?


> Since the source RPMs are mostly compatible between Fedora and SuSE, you
> might want to start there so 99% of the work will already be done for you,
> in fact, they may work as is as long as the build requirement names are the
> same.

Hopefully in the future someone might be interested in maintaining an RPM for 
some of these other Linux OS'es, making it super-easy for people to install and 
use.  I don't need that level of support but many do.

Consider setting up "Jenkins" to auto-build/test after each check-in, and to 
auto-build/release packages.  Makes things a lot easier in the long run.  I use 
Jenkins at work/home and am working on the auto-build/release methods for a 
project on SourceForge (CVS in this case, it's an older project).  I have it 
checking out/building after every SourceForge CVS check-in and letting me know 
if anyone breaks the build.  If I can get the packaging going under Jenkins I 
shouldn't have to build/release RPM's for that project ever again (wishful 
thinking, but mostly true).

-- 
Curt, WE7U.        http://wetnet.net/~we7u
The world DOES revolve around me:  I picked the coordinate system!"

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to