Solution: Creating and maintaining an eZ publish patch

While I have little hesitation in creating a patch directory structure within an the related extension or settings extension for the instance of that site installation there is a bit of work in keeping track of these modifications or patches for future upgrades.

Storing patch files in an extension

This makes patching fairly simple to repeat. Sometimes I use a patch file, sometimes I only use instances of the modified file and original file.

Path: [ Patch Base Path] + [ Version of eZ] + [ Relative Stock Path]

extension/ezexample/patch
extension/ezexample/patch/3.8
extension/ezexample/patch/3.9
extension/ezexample/patch/3.10
extension/ezexample/patch/3.10/kernel/shop/module.php
extension/ezexample/patch/3.10/kernel/shop/module.php.orig
extension/ezexample/patch/3.10/kernel/shop/module.php.diff

Example

Example of extension's which include kernel patches and or patch directory structure. (...)

Include path

Still, I can't remember if my tests in modifying the include_path were successful, I don't remember using it regularly after my first encounter with it.

The idea being you can add a file path to the php include path configuration variable which should allow you to be able to in affect override a specific stock file without having to actualy replace the stock file.

Example php.ini setting

Example of the php.ini setting requirered to override a stock eZ publish file (kernel or lib) (...)

External reference