As the title. I was suprised when I emerged mod_php and php was not built as part of the dependencies for the package.
Why were you surprised? What did you expect to be in mod_php that wasn't there?
I expected php to be a dependency of mod_php - i.e. if you emerge mod_php, php should be emerged if it is not already installed. OK, obviously, technically, php was not needed to *build and install* mod_php, however, it is needed to *run* mod_php. I had a glance at some of the emacs packages, which, technically can be installed without emacs as they are just lisp files, and they include virtual/emacs in their dependencies. To summarize: I would like to see dev-php/php in the DEPEND section for the next (and all future) ebuilds for mod_php.
I don't follow. You don't need dev-php/php to run dev-php/mod_php at all. I'd like to know about your experiences otherwise. If you are around presently, come to the Freenode IRC network, and message me (robbat2).
>> You don't need dev-php/php to run dev-php/mod_php at all. Oh! I am suprised but this could easily be true. I am embarassed to be wasting your time :-( >> I'd like to know about your experiences otherwise. OK, I need phpmyadmin, an interface to MYSQL written in PHP. I emerged phpmyadmin and 7 or 8 packages were built, but when I accessed the URL http://localhost/phpmyadmin, all I saw was the source for the index.php script. I have another computer on which this works perfectly, I have compared apache and php configs on the two machines and they are identical, so I tried to run the script from the command line, and found that php was not installed. I made the (now apparently wrong) assumption that not having php installed was was why apache wasn't parsing the php properly. I've never used IRC before, so I'll not be getting online. I think that this bug should be closed as INVALID, what do you think?
Right after you installed mod_php, there would have been a message with some further instructions. Either to add '-D PHP' to /etc/conf.d/apache2 if using Apache 2, or to run 'ebuild /usr/portage/dev-php/mod_php/mod_php-VERSION.ebuild config if using Apache1. After doing that and restarting the relevant Apache, it should work. Just seeing the source of phpMyAdmin is an indictaion that the mod_php module is not kicking in and something is slightly wrong in the Apache config.
Ah, I often miss that kind of message. I might nohup the emerge, especially if I am sshing in, and forget to check it. Or I might do the emerge in a konsole tab, but not return to it before I exit kde. I have an idea for a portage improvement, emailing those messages to someone, in case they get forgotten. Let me check the bug database... I have got phpmyadmin working now, a tiny apache config change IIRC. And I thought I'd changed everything :-) Thanks for your help, there is nothing wrong with my mod_php setup, it's all me :-)
The messages should be logged to wherever you have set portage to log to (in make.conf).
