[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#187460: 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-----



Reply to: