Re: Need some help to package apache-lingerd
I've worked a lot on apache-lingerd the past two days ; here is the result of my work : get this tarball : http://www.sukria.net/tarballs/apache-1.3.31-with-lingerd.tar.gz and run a dpkg-buildpackage inside ... Everything should compile nicely. You'll have every apache-* package (-ssl, --perl, ...) and a new one : apache-lingerd. Despite of the fact that each package compiles nicely, it remains a problem with the lingerd one : - no httpd.conf is installed (I cannot find how the Apache Team handle that file, it seems to be a nice trick to do with apache-lingerd.httpd.conf but I don't see exactly what). - there may be some problems with postinst and preinst scripts too... If someone, who knows how the Debian Apache Team works, can take an eye on my tarball, I would be gracefull. Thanks. PS : note that lingerd and apache-lingerd binaries are working very nice on my box, the last issue is to fix all the debian (pre|post)stuff and make sure evry conffile is installed correctly. -- * Alexis Sukrieh ([EMAIL PROTECTED]) disait : Alexis Sukrieh [EMAIL PROTECTED] * Another Linux Debian Geek Enthusiast * http://www.sukria.net
Re: Need some help to package apache-lingerd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexis Sukrieh wrote: | Hello there. | | I'm pretty interested in trying to package apache-lingerd, which has | been requested for more than 500 days now : | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187460 | | Could someone point me to some piece of docs on how the Debian Apache | Maintainers team bild their package ? eheh the truth is that our documentation is our debian/rules file. | | The fact is that lignerd needs the following steps to be packaged : | | First step : building lingerd : | | - tuning of config.h file | - user creation : 'lingerd' | - directory creation for hosting pidfile and unix domain socket | (/var/run/lingerd). | - compilation of lingerd binary and installation of it. This can be done easily afaict. | | Second step : patching Apache. | | - add some files to the apache src source tree | - patch some apache native files | - compile apache Amen.. this is a pain. I really suggest you to look at how we build apache. Take as example the fact that from the same source we create binaries for apache, apache-perl and apache-ssl, but if you really really need to create a patched apache i sugget to prepare everything carefully and coordinate with us. It is easier to build a new apache flavour from the same sources than having to upload a new one. The security team would have serious problems to handle (again) more than one apache source. | | Third step : | | - update the init.d startup script for apache : lingerd must be launched | before apache to work properly. if you start from the apache package check debian/pkgtemplates and the script that creates the final scripts. | | I'm sure that the team has a lot of guidelines to build such a package | but I cannont find any docs about this. as above.. read the source luke ;) | | Help will be welcome :) | | Fabio - -- user fajita: step one fajita Whatever the problem, step one is always to look in the error log. user fajita: step two fajita When in danger or in doubt, step two is to scream and shout. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBYYiRhCzbekR3nhgRAn9kAKCV8jPp0iU20wmuEvipphiOQeZIjQCdGDOT qJXBQPpDRJnmyzN8+9REP/A= =ktLr -END PGP SIGNATURE-
Re: Need some help to package apache-lingerd
* Fabio Massimo Di Nitto ([EMAIL PROTECTED]) disait : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexis Sukrieh wrote: | Hello there. | | I'm pretty interested in trying to package apache-lingerd, which has | been requested for more than 500 days now : | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187460 | | Could someone point me to some piece of docs on how the Debian Apache | Maintainers team bild their package ? eheh the truth is that our documentation is our debian/rules file. lol :) Ok. So I'll enable my debian-patched brain to extract doc from the debian/ stuff ;) | The fact is that lignerd needs the following steps to be packaged : | | First step : building lingerd : | | - tuning of config.h file | - user creation : 'lingerd' | - directory creation for hosting pidfile and unix domain socket | (/var/run/lingerd). | - compilation of lingerd binary and installation of it. This can be done easily afaict. Yep, that is definitely not the most difficult part, I agree. | Second step : patching Apache. | | - add some files to the apache src source tree | - patch some apache native files | - compile apache Amen.. this is a pain. I really suggest you to look at how we build apache. Take as example the fact that from the same source we create binaries for apache, apache-perl and apache-ssl, Yes, I think so, the best way is to start from the main debian-apache source. I will first look deeply inside in order to see what to do for a 'apche-lingerd'. | | Third step : | | - update the init.d startup script for apache : lingerd must be launched | before apache to work properly. if you start from the apache package check debian/pkgtemplates and the script that creates the final scripts. Ok, I'll take a look at that script. | I'm sure that the team has a lot of guidelines to build such a package | but I cannont find any docs about this. as above.. read the source luke ;) Hehe, I'll do it, and maybe the force bla bla ... :) -- Alexis Sukrieh [EMAIL PROTECTED] * Another Linux Debian Geek Enthusiast * http://www.sukria.net
