Robin Bowes wrote:
I'm just starting to look at OTRS on the CentOS platform. As is
quite usual for a package that does not have any/many core devs
using it on Redhat-flavours of linux (I assume), I have found that
the otrs-provided spec file does not do things quite right for the
Redhat-platform.
Fortunately, there is an OTRS RPM in the epel repository which has a
more suitable layout. I have successfully used this to rebuild the
2.30rc1 RPM.
Unfortunately, it is not quite right - specifically, it needs some
work on defining which files should me marked "%config(noreplace)"
so they are not zapped when the RPM is upgraded.
So, I'm looking for some feedback from the otrs team as to which
files should be considered "configuration" files and not replaced
when the RPM is upgraded.
Can anyone give me some guidance in this?
Sounds like a question for the dev list: http://lists.otrs.org/cgi-bin/listinfo/dev
We're using the RPM provided by OTRS on CentOS and that one works
fine for us, also regarding configuration files.
Nils Breunese.
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/
