Changes

From SME Server
Jump to navigationJump to search
Line 143: Line 143:  
stephen
 
stephen
 
----
 
----
 +
Thanks for these comments... I didn't know that we should not use events functions for our own events. Any chance to have an explanation? This sounds very weird to me (but there must be some reasons!)
 +
 +
Anyway, I will use domain-modify to expand all templates... I will try to (mostly) obey ;-)
 +
 +
Here's the actual createlinks perl script:
 +
#!/usr/bin/perl -w
 +
use esmith::Build::CreateLinks qw(:all);
 +
 +
# Templates to adjust
 +
templates2events("/etc/e-smith/sql/init/80ocs_mysql.sql",          qw(ocsglpi-update post-upgrade ));
 +
templates2events("/etc/e-smith/sql/init/82glpi_mysql.sql",        qw(ocsglpi-update post-upgrade ));
 +
templates2events("/etc/e-smith/sql/init/84ocs-glpi.sql",          qw(ocsglpi-update post-upgrade ));
 +
templates2events("/etc/httpd/conf/httpd.conf",                    qw(ocsglpi-update post-upgrade ));
 +
templates2events("/etc/ocsinventory-agent/ocsinv.conf",            qw(ocsglpi-update post-upgrade ));
 +
templates2events("/opt/inventory/glpi/config/config_db.php",      qw(ocsglpi-update post-upgrade ));
 +
templates2events("/opt/inventory/ocs/ocsreports/dbconfig.inc.php", qw(ocsglpi-update post-upgrade ));
 +
# Services to restart
 +
safe_symlink("restart", "root/etc/e-smith/events/ocsglpi-update/services2adjust/httpd-e-smith");
 +
safe_symlink("start",  "root/etc/e-smith/events/ocsglpi-update/services2adjust/mysql.init");
 +
As you can see, there's a loooong list as all is templated!
 +
 +
 +
I will also delete all chat in the RPM. That's an old habits of mine...
 +
 +
About the help file, I remember reading that it must be placed into www/ocs/files/guide.pdf (else I would have put this file in /usr/share/doc/) so we cannot delete this file from the RPM :'(
498

edits

Navigation menu