Re: compile vs. apt-get (dpkg)
- To: Grischa Schuering <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: compile vs. apt-get (dpkg)
- From: Craig Sanders <firstname.lastname@example.org>
- Date: Thu, 1 Mar 2001 14:31:14 +1100
- Message-id: <20010301143114.N6961@taz.net.au>
- In-reply-to: <F6B6C0113FA7B94D86B34CB9493D02F30A2613@atlas._msdcs.inity.de>; from email@example.com on Thu, Mar 01, 2001 at 12:53:58AM +0100
- References: <F6B6C0113FA7B94D86B34CB9493D02F30A2613@atlas._msdcs.inity.de>
On Thu, Mar 01, 2001 at 12:53:58AM +0100, Grischa Schuering wrote:
> I have asked this question before....
> I am a fan of the apt-get update feature... But right now I need to
> compile a package (apache) from source, because I need to compile
> into the source a few modules, which are not available as precompiled
> I undestand, that I loose all apt functionality, when starting to
> compile my own source. What way is the best to deal with a situation
> like this ???
others have suggested building your own .deb packages of apache. that's
a good option.
another good option is to build your own .deb packages for the
unpackaged modules. it's pretty easy to do.
download the debianised source for one of the simpler apache module
packages (e.g. libapache-mod-auth-pam). study the debian/rules file and
you'll notice that it's actually quite easy to make an apache module
BTW, you'll need the apache-dev package installed, as well as a
reasonably full suite of developer tools and libraries (gcc, make,
dpkg-dev, debhelper, libc6-dev, etc)
craig sanders <firstname.lastname@example.org>
GnuPG Key: 1024D/CD5626F0
Key fingerprint: 9674 7EE2 4AC6 F5EF 3C57 52C3 EC32 6810 CD56 26F0