On 01/04/2016 11:11 AM, Peter Stuge wrote: > > So pkg_postinst for >=eselect-php-0.8.1 should say something, but > ideally also the invocation - but I don't know if eselect-php is also > code or only data managed by eselect?
The pkg_postinst is already there. The eselect-php routines are bash code so theoretically we can do anything we want. How do people feel about making eselect-php spit out a warning every time the apache2 module is messed with? >> >> Which init script? > > For Apache. > >> You don't want to e.g. kill working php-5.x installations for people >> who have apache keyworded ~arch. > > IMO that would be a much lesser evil than serving source in another > case, as long as it is clear how to unkill (sed s,PHP5,PHP,) the setup. > It wouldn't be that simple; at the very least, those people would have to keyword eselect-php, upgrade it, run it, and fix their config. To do that properly would make eselect-php a dependency of the new apache, and that's wrong.
