In the enclosed tar.bz2 file, I have enclosed an ebuild for the newest version of Apache, complete with the file apache-builtin-mods for choosing what modules to compile as what. The file works if you extract to /usr/portage/net-www, then you can install with emerge net-www/apache2
Created attachment 1725 [details] The compressed form of the ebuild + associated files
Created attachment 1726 [details] UPDATED: The compressed form of the ebuild + associated files Before the ebuild didn't create the conf.d files or init.d files This makes attachment 1725 [details] obsolete
carpaski; if you have some time/priority for this, please go ahead and handle it. unfortunately i dont have much time to mess with apache2 at the moment. i will of course be lurking in the background, watching, ;-) if it could follow the layout/direction of the apache-1 port, that'd be nice. i havent looked at this yet, but where is it storing the modules? It shouldnt be /usr/lib/apache, becasue thats where apache-1 will store its. what about /etc ? I hope it's using /etc/apache2 or similar? Basically, if I did have time, I'd be making sure this packaage can be installed alongside and work alongside an apache-1 install. Debian is doing similar things I believe. Gotta run, thats just a few things I can think of for now. Oh, and anything DEPENDing on net-www/apache in the portage tree, will probably have to be tweaked. Specifically, anything doing like >=net-www/apache-1.3 will have to be looked at, to make sure it really doesnt need =net-www/apache-1* instead. stuff like the net-www/mod_* packages comes to mind. Donny
Created attachment 1753 [details] UPDATED: apache2-2.0.39-r1.tbz2 - tar.bz2 file of apache2-2.0.39-r1 ebuild Updated to exist side by side with apache 1 Package name: net-www/apache2 Sys Config Dir: /etc/apache2 Info Dir: /usr/share/info Man Dir: /usr/share/man Everything else is in /usr/local/apache2: Bin dir: /usr/local/apache2/bin Modules dir: /usr/local/apache2/modules et cetera
Ok... I started going through this but got side tracked... Sorry about the delay. You can't use a variable before you define it... RDEPEND Don't submit it with skel comments. Paths should NOT touch /usr/local Makes sure they aren't expanded on top of prefix. Check the 1.3.26 ebuild for path examples Check the apache 1.3.26 ebuild for user and group discovery info. EVERYTHING USEFUL should be built in, unless you can provide a way to set it up beforehand or it can be done with USE flags. I'm not sure about the suexec thing, unless it comes disabled in the config.
Some version I modified is in portage.