Hi all! 2011/6/22 David Baelde <[email protected]>: > Hi Brandon, thanks for looking into this and proposing your help. I > don't know much about Debian packaging, but I can tell you that we're > planning a beta2 release in the next few days, and Romain will ship > the Debian package immediately after that. Concerning the daily > builds, I don't know what's up.
Thanks Brandon for proposing your help. It could be precious in these times of so little spare time for us :-) Concerning the debian packages, there are two different things: * The official package: The official debian/ubuntu liquidsoap package is built not using the full tarball. For this package, dependencies are packaged independently, e.g. libmad-ocaml-dev and then the liquidsoap package depends on those at build-time. The official package is quite tricky. We are actually planning a support for plugins, that is to provide a seperate package for each optional functionality, such as SDL, lastfm, etc.. This makes the packaging quite tricky and requires coordination with the ocaml team. A good news concerning the official package is that, starting with the coming beta2, the official package will be able to dynamically load lame and aacplus, which means that regular users won't have to recompile liquidsoap just to get MP3 or AAC+ encoding enabled! * The daily packages (and the old full package): Those packages are much more simple. They are built directly using the -full tarball or the hg repository. They do not have plugins and, thus are much more simple to maintain. The full packages where originally intended to provide a compiled liquidsoap with mp3 support enabled. As explained before, these packages are no longer necessary now. However, the daily packages have proved to be extremly useful in order to get quick feedback on the recent developement code and to ease the process of testing recent builds for a regular users. The only reason why they are not maintained is lack of time and general tiredness. When moving the server a year ago to an amd64 architecture, I though it would be useful and fun to enable daily builds for both i386 and amd64. This, in fact, turned out to be much more difficult than I though and I finally got bored and lacked time to properly finish it. I would be more than happy to give more informations and any approriate access to anyone interested in maintaining the daily packages! There is come code laying around at this place: https://savonet.svn.sourceforge.net/svnroot/savonet/utils/daily-build Feel free to have a look at it :) If you want to take over the daily packages, all you would need is a machine with the required dependencies installed and a cron script to build the package every day. I would not recommend trying to build a i386 package out of an amd64 system, so two machines would be ideal. My server can do the amd64 one while another one could do the i386 one.. Romain ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
