| 1 |
On Wed, 15 Sep 2004 16:48:53 -0400, Doug Goldstein <cardoe@g.o> wrote: |
| 2 |
> I'm actually the maintainer of a couple of Apache modules (currently not |
| 3 |
> included in Portage but shortly I'll look to include them when I |
| 4 |
> stablize them a bit more) that I have the codebase support both Apache 1 |
| 5 |
> and Apache 2 through a mess of #DEFINE and ./configure but I did that to |
| 6 |
> make it easier for users. With this scheme the package would have to |
| 7 |
> appear in two catagories under the same name and it would conflict with |
| 8 |
> the other one and provide an ugly mess. Heck.... every package... like |
| 9 |
> emerge mod_perl wouldn't even work.. it'd give you an ugly message |
| 10 |
> saying which one? www-apache1/mod-perl or www-apache2/mod-perl... Not |
| 11 |
> ideal in my book. There's got to be a better way about this. |
| 12 |
|
| 13 |
Don't mean to nitpick, but mod_perl is actually dev-perl/mod_perl and |
| 14 |
unless you're going KEYWORDS="~arch", isn't happy with apache2 ;-) on |
| 15 |
a standard x86 box (if you're on amd64 or alpha, it's not masked) |
| 16 |
either way, if you're brave you've got a choice: |
| 17 |
|
| 18 |
[root$box]::mod_perl> emerge -upv mod_perl |
| 19 |
|
| 20 |
These are the packages that I would merge, in order: |
| 21 |
|
| 22 |
Calculating dependencies ...done! |
| 23 |
[ebuild N ] dev-perl/libnet-1.16 68 kB |
| 24 |
[ebuild N ] dev-perl/Crypt-SSLeay-0.49 114 kB |
| 25 |
[ebuild N ] dev-perl/libwww-perl-5.79 +ssl 219 kB |
| 26 |
[ebuild N ] sys-libs/db-4.0.14-r3 +doc -java -tcltk 2,638 kB |
| 27 |
[ebuild N ] dev-libs/mm-1.2.1 211 kB |
| 28 |
[ebuild N ] net-www/apache-1.3.31-r3 +pam 3,146 kB |
| 29 |
[ebuild N ] dev-perl/mod_perl-1.27-r4 +ipv6 363 kB |
| 30 |
|
| 31 |
Total size of downloads: 6,762 kB |
| 32 |
|
| 33 |
Now that that's out of the way... |
| 34 |
DEPEND=" apache? ( www-apache1/apache ) |
| 35 |
apache2? ( www-apache2/apache )" |
| 36 |
farther on down the ebuild: |
| 37 |
if use apache; then |
| 38 |
einfo "Building for Apache v1.x" |
| 39 |
myconf="${myconf} --build-for-apache1" |
| 40 |
fi |
| 41 |
|
| 42 |
I hope you get the point. This isn't as much of a disaster as you're |
| 43 |
thinking it is. If you don't need to be put in either catagory, |
| 44 |
perhaps a 3rd that is a little more generic for things that don't fit |
| 45 |
anywhere else? apache-common? |
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives