Couldn't we make an installer that uses 'patch' to modify the required files?
Here's how it plays out in my mind:During Testing/Development:
To make a diff:
We keep a copy of an unmodified version of Control_Center.pm and drakconf.real somewhere.
When we need to modify either of the two files, we make another copy of the unmodified version.
Then we make our changes in one of the two identical files.
We then use 'diff' to generate a diff file that can be applied with patch.
For sanity's sake, It is important that each diff only provides changes for a specific app.
The archive for the program would contain the one or two diff files that add the changes for that program.
The installer would then apply the diff files using 'patch' and do other necessary stuff.Final Release (RPM):
All of the current patches are applied to the source code of the SRPMs containing drakconf.real and Control_Center.pm and the RPMs are rebuilt.
The actual perl scripts for the programs are packaged into their own RPMs.
Because if the perl script isn't installed, the PCC will ignore it and will not display an icon for it.
The PCC currently does this for some other non-existing apps.
Anyway, that's my idea.
Tell me if there is anything wrong with it. (Note that the "make a diff" process should only have to be done once per app.)