| 1 | From time to time, we find that modifying configuration files isn't enough to enact the changes we need to build a Debathena system. In cases like these, we need to modify the packages themselves that we're configuring. In the past, some reasons we've needed to modify upstream-distributed packages include: |
| 2 | * Enabling krb4 support in `evolution-data-server` or `alpine` before the mail servers supported krb5 authentication. |
| 3 | * Modifying the `lprng` package, renaming commands like `lpr` to `mit-lpr` so they don't conflict with the `cups-bsd` package. |
| 4 | |
| 5 | One of the great strengths of the `config-package-dev` development model is that mechanisms such as `DEB_TRANSFORM_FILES` allow you express just your changes, as opposed to the entire result. The Debathenificator framework was designed to serve this purpose for modifying whole packages. |
| 6 | |
| 7 | The Debathenificator framework itself lives in source:/trunk/debathena/third/common, and individual Debathenified packages live in other subdirectories of source:/trunk/debathena/third. |