On Fri, Apr 29, 2011 at 8:51 AM, Dave Neary <dne...@maemo.org> wrote: > Ludovico, can you make a .tar.gz based on that tag that I can put on the > site, and from which we can start making Linux packages & the binary > builds for Windows & Mac? > > For the .tar.gz, it would be good to remove any unchanged dependencies,
Do you mean any directory in libs/3rdparty that has not changed since 2.2? But this would complicate packaging, because one tarball is not enough for compiling qutecom. Plus it is something that has to be done by hand... > I think (we can guild Windows & Mac binaries from the tagged > repository), ok, so, you want to make a linux-only source tarball, correct? > but to leave anything currently black-balled by Debian > legal in the .tar.gz - IMHO these can be removed in a second step for > Debian packages. if we remove the windows stuff, the only problematic one left is iLBC. Plus I was removing all 3rd-party libraries that we were not using, but it makes sense to keep them for the generic linux source tarball. So here is the tarball: http://epicfail.cs.ucsb.edu/~cavedon/qutecom-2.2.1.tar.gz and the script I used to generate it: http://epicfail.cs.ucsb.edu/~cavedon/qutecom-2.2-make-tarball.sh It compiles and runs successfully as is (except for applying http://trac.qutecom.org/attachment/ticket/287/new-videodev.patch) on the latest Debian unstable. $ sha1sum qutecom-2.2.1.tar.gz qutecom-2.2-make-tarball.sh 14ff024101d5630726bdb847231ce42ff7e96ad7 qutecom-2.2.1.tar.gz 04361c5926b7c2111bedf0bff941e4be35f9ec64 qutecom-2.2-make-tarball.sh Let me know if it is ok for you, Cheers, Ludovico _______________________________________________ QuteCom-dev mailing list QuteCom-dev@lists.qutecom.org http://lists.qutecom.org/mailman/listinfo/qutecom-dev
