Not Logged in - No Account?
Don't have an account? Registering an account with us allows you to post to the forums, easily track new posts, subscribe to threads, pm (private message) other forum members, and receive periodic news letters (you can opt out if you desire). Once you are logged in this message will no longer appear. If you don't have an account, you can create one by registering here. Lost your password, request a new password. We respect your privacy which means we collect minimal information when you register and we do not resell that information or use it in any objectionable way. You can review our privacy policy for full details.
rpm packaging and the framework module
Hi all
I make rpm freepbx modules for my own use on fedora/redhat/centos machines.
I usually include a set of up-to-date modules in my rpm package. I often need to apply small patches, and often my changes are overwritten by the code in the framework module. So at packaging time, I have to apply the same patches both to freepbx itself and to the framework module. It's a bit annoying and error-prone since I have to look for patches that touch files that are in the framework module.
So the question is: is there a reliable way to install the framework module to a freepbx source tree, before installing freepbx?
Something like this:
untar freepbx
apply the framework module
redo the freepbx tar.gz archive with the up-to-date framework included
Thanks
not really, the framework
not really, the framework module is not really a module. You can think of it as another form of install_amp. There is an amportal.conf setting to disable Module Admin and then only use your packages, that's about it.
Philippe Lindheimer - FreePBX Project Leader
FreePBX Training Opportunities - Click Here
Get Official Paid Support - Click Here
I already set
I already set AMPEXTERNPACKAGES=true, if that's what you are talking about, because I want to use a new package release to update my freepbx installations. My problem is different. in the post install script to activate the modules.
At package building time, I download the modules I need, and unpack them in amp_conf/htdocs/admin/modules.
Then I simply put some module_admin install
Everything seems to work fine, if it was not for the framework module which updates some freepbx core files (and I like that, because I like to have bugfixes) but it overwrites even my changes I previously applied to the same freepbx core files.
One recent example: I need to patch amp_conf/htdocs/admin/functions.inc.php . If I only patch the version of the file from freepbx-2.4.0.tar.gz (for example), then apply Freepbx Framework v. 2.4.1.0 (which was out prior to freepbx-2.4.1), the functions.php file gets overwritten, and my changes are lost.
It seems that instead of patching freepbx at package building time, and then applying the freepbx framework at install time, I should apply the freepbx framework, then apply my patches both at package building time. Am I right? Do you see some way to achieve this? In other words: am I safe if I unpack the freepbx tar.gz, then rewrite some files with the ones from the framework module, than build my package?
Thanks