RE: compile vs. apt-get (dpkg)
Can someone tell me what to do when apache sources are downloaded ?? How do we make a package. Sorry for asking this question, but I really don't know what to do. Thanks Grischa -Original Message- From: Schmitt David [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 01, 2001 12:11 PM To: [EMAIL PROTECTED] Subject: Re: compile vs. apt-get (dpkg) On Thu, Mar 01, 2001 at 02:31:14PM +1100, Craig Sanders wrote: 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) get task-debian-devel and take a look at the 'Build-Depends' Line in the debian/control file of the unpacked package. There is also a packaging-manual. Good luck! Regards, David Schmitt -- Suche Partnerin frs Leben: bin gutaussehend, kinderlieb, kann kochen, hasse Fuball, liebe langes Vorspiel und lge notorisch -- Franz Reitmeier [EMAIL PROTECTED] in at.anzeigen.kontakte MID: 96s2tk$q67$07$[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compile vs. apt-get (dpkg)
On Thu, Mar 01, 2001 at 05:43:58PM +0100, Grischa Schuering wrote: Can someone tell me what to do when apache sources are downloaded ?? How do we make a package. For the necessary tools you will need to [root@devel ~] apt-get install task-debian-devel Then go into your development dir and get the source: [user@devel ~] cd packages [user@devel ~/packages] apt-get source apache You need deb-src lines in your sources.list for this to work. Now cd into the newly created directory and check, that you have everything you need: [user@devel ~/packages/apache-1.3.14] cat debian/control | grep Build-Depends Install the packages (with appropriate versions) on your system. For apache-1.3.14 this is: debhelper, libmysqlclient10-dev, postgresql-dev, sharutils, libdb2-dev (= 2.7.7-2.1). Having set up all correctly you should be able to build the default package now: [user@devel ~/packages/apache-1.3.14] dpkg-buildpackage -rfakeroot -us -uc Now, lean back and get yourself some coffee (or faster H/W ;) If the correct versions of the Build-Dependencies are not available for your target-release you will have to recompile and install them too. Meanwhile you can take a look at the debian/ directory where all files which control the debian-part of the build-process reside. The most important are control and rules. For a very thorough description take a look at the packaging-manual package. If you want to make your own package from upstream sources take a look at dh_make or (in case of apache modules) search for similar packages and take a look at their source (especially the debian/ directory). If you need further help, you can ask specific questions via PM, since I think this is getting OT here. Regards David. -- Suche Partnerin frs Leben: bin gutaussehend, kinderlieb, kann kochen, hasse Fuball, liebe langes Vorspiel und lge notorisch -- Franz Reitmeier [EMAIL PROTECTED] in at.anzeigen.kontakte MID: 96s2tk$q67$07$[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compile vs. apt-get (dpkg)
On Thu, Mar 01, 2001 at 02:31:14PM +1100, Craig Sanders wrote: 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) get task-debian-devel and take a look at the 'Build-Depends' Line in the debian/control file of the unpacked package. There is also a packaging-manual. Good luck! Regards, David Schmitt -- Suche Partnerin fürs Leben: bin gutaussehend, kinderlieb, kann kochen, hasse Fußball, liebe langes Vorspiel und lüge notorisch -- Franz Reitmeier [EMAIL PROTECTED] in at.anzeigen.kontakte MID: [EMAIL PROTECTED]
RE: compile vs. apt-get (dpkg)
Can someone tell me what to do when apache sources are downloaded ?? How do we make a package. Sorry for asking this question, but I really don't know what to do. Thanks Grischa -Original Message- From: Schmitt David [mailto:[EMAIL PROTECTED] Sent: Thursday, March 01, 2001 12:11 PM To: debian-isp@lists.debian.org Subject: Re: compile vs. apt-get (dpkg) On Thu, Mar 01, 2001 at 02:31:14PM +1100, Craig Sanders wrote: 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) get task-debian-devel and take a look at the 'Build-Depends' Line in the debian/control file of the unpacked package. There is also a packaging-manual. Good luck! Regards, David Schmitt -- Suche Partnerin fürs Leben: bin gutaussehend, kinderlieb, kann kochen, hasse Fußball, liebe langes Vorspiel und lüge notorisch -- Franz Reitmeier [EMAIL PROTECTED] in at.anzeigen.kontakte MID: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: compile vs. apt-get (dpkg)
On Thu, Mar 01, 2001 at 05:43:58PM +0100, Grischa Schuering wrote: Can someone tell me what to do when apache sources are downloaded ?? How do we make a package. For the necessary tools you will need to [EMAIL PROTECTED] ~] apt-get install task-debian-devel Then go into your development dir and get the source: [EMAIL PROTECTED] ~] cd packages [EMAIL PROTECTED] ~/packages] apt-get source apache You need deb-src lines in your sources.list for this to work. Now cd into the newly created directory and check, that you have everything you need: [EMAIL PROTECTED] ~/packages/apache-1.3.14] cat debian/control | grep Build-Depends Install the packages (with appropriate versions) on your system. For apache-1.3.14 this is: debhelper, libmysqlclient10-dev, postgresql-dev, sharutils, libdb2-dev (= 2.7.7-2.1). Having set up all correctly you should be able to build the default package now: [EMAIL PROTECTED] ~/packages/apache-1.3.14] dpkg-buildpackage -rfakeroot -us -uc Now, lean back and get yourself some coffee (or faster H/W ;) If the correct versions of the Build-Dependencies are not available for your target-release you will have to recompile and install them too. Meanwhile you can take a look at the debian/ directory where all files which control the debian-part of the build-process reside. The most important are control and rules. For a very thorough description take a look at the packaging-manual package. If you want to make your own package from upstream sources take a look at dh_make or (in case of apache modules) search for similar packages and take a look at their source (especially the debian/ directory). If you need further help, you can ask specific questions via PM, since I think this is getting OT here. Regards David. -- Suche Partnerin fürs Leben: bin gutaussehend, kinderlieb, kann kochen, hasse Fußball, liebe langes Vorspiel und lüge notorisch -- Franz Reitmeier [EMAIL PROTECTED] in at.anzeigen.kontakte MID: [EMAIL PROTECTED]
compile vs. apt-get (dpkg)
Hello, 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 packages.. 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 ??? Thanks, Grischa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compile vs. apt-get (dpkg)
quote who="Grischa Schuering" 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 ??? apt-get source apache (you must have deb-src lines in your /etc/apt/aources.list) Then you can modify the build rules, diffs, etc., and build the package as per normal. Of course, if you're adding Free modules into the mix, send your patches back to the maintainer. :) [ The other way to do it is to compile then install using stow, but that's pretty urky with apache, and not as productive. ] - Jeff -- [EMAIL PROTECTED] - http://lazarus.aphid.net/ -- o/~ In spite of all those keystrokes, you're addicted to vim. *ka-ching!* o/~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
compile vs. apt-get (dpkg)
[...] GS I undestand, that I loose all apt functionality, when starting GS to compile my own source. What way is the best to deal with a GS situation like this ??? "Best" depends on your circumstances. If you are willing to invest the time, the best way is making your own .deb, bumping the version by an NN: prefix (or by some other method that I don't know) and using that. The advantages are numerous: you can install it on other boxes, you can remove it painlessly, .deb's that need http servers will still install (since your apache package is providing it) without override switches. If you change the version number properly, apt-get will leave your package when the apache in the real distribution is updated. I have had to do this once for squid a while ago. The documentation (check the doc portion of the web site) was not great, but starting with an already packaged program makes things easy. Things may have improved since then. cheers, BM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
compile vs. apt-get (dpkg)
Hello, 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 packages.. 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 ??? Thanks, Grischa
Re: compile vs. apt-get (dpkg)
quote who=Grischa Schuering 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 ??? apt-get source apache (you must have deb-src lines in your /etc/apt/aources.list) Then you can modify the build rules, diffs, etc., and build the package as per normal. Of course, if you're adding Free modules into the mix, send your patches back to the maintainer. :) [ The other way to do it is to compile then install using stow, but that's pretty urky with apache, and not as productive. ] - Jeff -- [EMAIL PROTECTED] - http://lazarus.aphid.net/ -- o/~ In spite of all those keystrokes, you're addicted to vim. *ka-ching!* o/~
compile vs. apt-get (dpkg)
[...] GS I undestand, that I loose all apt functionality, when starting GS to compile my own source. What way is the best to deal with a GS situation like this ??? Best depends on your circumstances. If you are willing to invest the time, the best way is making your own .deb, bumping the version by an NN: prefix (or by some other method that I don't know) and using that. The advantages are numerous: you can install it on other boxes, you can remove it painlessly, .deb's that need http servers will still install (since your apache package is providing it) without override switches. If you change the version number properly, apt-get will leave your package when the apache in the real distribution is updated. I have had to do this once for squid a while ago. The documentation (check the doc portion of the web site) was not great, but starting with an already packaged program makes things easy. Things may have improved since then. cheers, BM
Re: compile vs. apt-get (dpkg)
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 packages.. 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 package. 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 -- craig sanders [EMAIL PROTECTED] GnuPG Key: 1024D/CD5626F0 Key fingerprint: 9674 7EE2 4AC6 F5EF 3C57 52C3 EC32 6810 CD56 26F0
