I've done a search on this but couldn't find any topics covering it...

I'm currently getting my servers configured/installed on my Gentoo Linode, and one of the things that I'd like to set up is AxKit. However, in order to do this I need Apache 1.3.x instead of 2.x. If followed the instructions here --

http://forums.gentoo.org/viewtopic.php?t=78915&highlight=axkit

-- and it works on the Gentoo install I have running on VMWare here, but not on the Linode.

Summary:

# mkdir -p /etc/portage
# echo ">=net-www/apache-2" >> /etc/portage/portage.mask

Any emerge -p package I do that relies on Apache still reports that Apache2 will be installed.

Am I missing something? Is there a different way to specify masks for the Gentoo Linodes?

Take a look at your USE flags. The "apache2" flag controls which
version Portage wants to emerge.

I fired up ufed and it showed that the apache2 use flag was cleared. Just to be sure I took a look at /etc/make.conf, /etc/make.profile/make.defaults and /etc/make.globals, but it wasn't in there either. (Also, nothing in $USE.)

Any other suggestions?

My apologies for not looking closer at your problem. I don't know why
your mask file isn't working. Probably somewhere in the Gentoo Portage
forums there's an answer (probably posted by Genome, too).

Anyway, for what it's worth, here's another suggestion:

Edit the ebuild in /usr/portage/dev-perl/Apache-Test and
the DEPEND line to remove the net-www/apache requirement?

I THINK this will work for now but ou'll have issues in the future if Apache-Test gets changed in an emerge sync.

Another option is to show the net-www/apache requirement is
satisfied. I think there's some discussion in the main portage docs
about doing this. This would be cleaner but I don't know specifics.
Something about stub ebuilds?

Apparently Apache-Test's latest version compiles with a version bump.
See Gentoo Bugzilla http://bugs.gentoo.org/show_bug.cgi?id=30228

So ... if you're going to hack the ebuild anyway, why not build the
latest version while you're at it? Copy the current ebuild and up the
version.

Ugh. Blame it on not enough sleep... wrong filename.

Thanks for your help.

You're welcome. (For more sleep set USE="+sleep")