Summary: | PHP ebuilds: Include custom php.ini file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timo A. Hummel <privat> |
Component: | New packages | Assignee: | PHP Bugs <php-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Timo A. Hummel
2011-03-24 17:25:04 UTC
sounds like someone needs to learn to use dispatch-conf I can't see how your comment helps the discussion, Spanky, but feel free to enlighten us. if you actually read the manual you'd see that dispatch-conf takes care of backing up previous files. so when you do something stupid, you can easily undo the update. fix your tool usage. mommy, this fork hurts when i poke my tongue. let's make all forks spoons! I have read the manual. Even if I didn't, everyone should know how to make backups. I am not asking to make a fork a spoon. I am asking to include a bit helpful to make a fork a better fork. If you have nothing to say than sarcastic comments because you are unable to catch the issue, I'd recommend to not comment on such issues. too bad you missed the point. instead of trying to "fix" things that arent broken because you keep fat fingering a tool, use a tool that works for people with fat fingers. I did not ask to fix something. I asked to include a bit of convenience documentation. Too bad you missed that. (In reply to comment #0) > Whenever you upgrade PHP, a new configuration file is installed in-place. It is not installed in-place. Configuration files are always preserved until you manually merge them using dispatch-conf. Also ext-active is reserved for symlinks to ext so that php will not try to load extensions that have been unmerged, but still allow users to keep their extension configs preserved in the ext directory. Anyways, thanks for the suggestions. |