Hi, Ludovico Cavedon wrote: > I completely agree with you that we should include 3rd party libs in > the tarball, but... > Do we know which parts of the code are straight from upstream with no changes?
Everything in /libs/3rdparty should be unchanged (right? ;) ). > I remember we used to have patches to libpurple. We do have a patch to libpurple to add an extra API call we needed to update the status on all connected accounts at the same time. I believe we submitted it back in the Wengo days but it was rejected. > I am also afraid that recovering this information from the repository > is not possible/easy. > Best way would be probably a hand "diff -r" :( eh, yeah. Not ideal. Especially since I'm not sire we know exactly what versions are in the repository :} >> I thought this was what your script did, more or less? > > More or less. My script was removing > -all binary stuff > -windows & mac only libraries > -libraries with does not need to be compiled into qutecom (but we can > link qutecom against their system version) Sounds good. >>>> I think (we can guild Windows & Mac binaries from the tagged >>>> repository), >>> ok, so, you want to make a linux-only source tarball, correct? >> Basically, yes. In reality, it won't be Linux only, it will be for every >> platform, but will not include any dependencies that you'll have to >> build yourself. It'll just be easier for Linux developers. > > It might be very complicated to build such dependencies in a proper > way for compilation with qutecom on mac and windows. > They also need to be copied in the proper spot in the qutecom build > tree, and I do not think we have documentation for that... Let me ask the question to subscribers of this list: how many of you will build a release tarball for Windows, rather than pulling the sources from hg? If there's demand for it, then we should work to get it right, but I don't think there will be demand. Either people will download the Windows binaries we publish, or they will be compiling from Mercurial. I think only Linux packagers will care about the source tarball. > IMHO, the only two usable way to distribute a source package are: > -old-style tarball with precompiled binaries (checkout of the repo) > -linux-only, stripped down tar.gz (see link in my previous email) > -or both :) I favour Linux only, and if we get queries on how to build it on Windows, we can deal with them then. Thanks, Dave. -- Dave Neary dne...@free.fr Tel: +33 9 51 13 46 45 Cell: +33 6 77 01 92 13 _______________________________________________ QuteCom-dev mailing list QuteCom-dev@lists.qutecom.org http://lists.qutecom.org/mailman/listinfo/qutecom-dev
