It seems that mod_php no longer requires php to run/compile. at least according to my emerge output: # emerge -p mod_php [ebuild R ] dev-php/mod_php-5.0.3-r2 # emerge -p php [ebuild N ] dev-php/php-5.0.3-r1 The problem is following: when i try to emerge squirrelmail for instance, I get: [ebuild N ] dev-php/php-5.0.3-r1 [ebuild N ] dev-php/PEAR-DB-1.6.8 [ebuild R ] mail-client/squirrelmail-1.4.4 I.e the system doesn't recognize mod_php as providing php. this is because mod_php-5.0.3-r2.ebuild contains PROVIDE="virtual/httpd-php-${PV}" Should this not contain PROVIDE="virtual/php" now ? Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: mod_php should provide virtual/php
no, this output is entirely correct! Installing PEAR classes requires the /usr/bin/php binary (this is what the virtual/php means). If you picked a webapp that doesn't need any PEAR classes, you could install it without having dev-php/php.
hi Robbat2, yeah i noticed that after posting,.. most likely the packages that only run in a web environment (like squirrelmail) should have their RDEPEND or DEPEND changes to mod_php's PROVIDE.. right? Greets Gabe
perhaps (to virtual/httpd-php), but that's a longer-term project that is only planned for future (other things need to get done first).
