Hi, > But ini files with absolute > paths are important for setup. I propose to copy theses ini > files to "*d-for-test.ini"
why do we need another set of config files? Packagers can apply patches to relative-path-ini-files when they build an rpm. I think that's the common way how packages get distribution-specific paths. Look at the attached patch file. It changes the ini-files like Olivier did. In the spec-file we write: ... Source0: http://ftp.monitoring-fr.org/JEAN/shinken-%{version}.tgz Source1: %{name}-configs.tar.bz2 Patch0: shinken.config-abs-paths-centos.patch # local or also on ftp-server ... %setup -q -n %{name} %{__tar} xjf %{SOURCE1} # now replace ../var with /usr/local/... %patch0 -p1 %build This way, you can launch processes immediately, for-test-ini-files are not necessary and we have rpms with absolute paths. Gerhard __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 5366 (20100814) __________ E-Mail wurde gepruft mit ESET NOD32 Antivirus. http://www.eset.com
shinken.config-abs-paths-centos.patch
Description: Binary data
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Shinken-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shinken-devel
