3 ms·
nice post, but it misses out the bit about documenting the change, making sure that your distribution doesn't suddenly nuke your changes when it does an upgrade
by davidarkemp2 14y ago
nice post, but it misses out the bit about documenting the change, making sure that your distribution doesn't suddenly nuke your changes when it does an upgrade, finding programmers who can work on your codebase given your customisation of php...
It's a useful post, but I'd like a but more warning that you really don't want to do this unless your proposing on either contributing this back into the core codebase, or forking php - something that can't be done likely. It reads a bit too much like this is something everyone should be doing.
- maratd 14y ago> or forking php - something that can't be done likely Why? PHP is on Github now. Merging changes from upstream should be relatively trivial as long as you don't get too excited about adding/subtracting stuff.
- ihsw 14y agoPHP is not on Github, the project on Github is simply a mirror. http://git.php.net/ http://git.php.net/ https://github.com/php/php-src https://github.com/php/php-src EDIT: They are receptive pull requests, though.
- lysol 14y agoI think a person capable of performing this sort of change against PHP is also capable of understanding that implicitly.