Q: The SuSE Package Conventions Documentation
Hi all, reading documentation for builing own RPMs, I found the helpfull "SuSE Package Conventions" documentation (see http://www.suse.de/~mmj/Package-Conventions/ ). I have a problem with /etc/sysconfig/ config files. Before writing sysconfig files for an own RPM, I played a little bit with the zope RPM package from SuSE 8.0. I installed it, then I put a ZOPE_WEVDAV_PORT="8088" variable to the original /etc/sysconfig/zope file. BIG Problem: YaST2 shows the ZOPE_WEVDAV_PORT variable in the "etc" section of the sysconfig tree (this grafic-interface-thing of sysconfig). I tried it with several other packages. All additional variables to sysconfig files will be put to "etc" section. What's going wrong here? To be sure, I build a new zope RPM using the original SuSE src.rpm. I add ZOPE_WEVDAV_PORT="8088" to the SOURCE/sysconfig.zope file, built a new binary rpm and installed it. Same problme. My new ZOPE_WEVDAV_PORT is placed in "etc" section in the sysconfig tree. All other ZOPE variables are placed in right zope section. This drives me realy crazy!!!! BTW: How do I create subfolders in the yast2 sysconfig tree? Thanks for helping Marcus -- Marcus Schopen (0> P.O. Box 10 25 25 //\ Deutsche Zope User Group D-33525 Bielefeld V_/_ www.dzug.org
Marcus Schopen wrote:
Hi all,
reading documentation for builing own RPMs, I found the helpfull "SuSE Package Conventions" documentation (see http://www.suse.de/~mmj/Package-Conventions/ ).
I have a problem with /etc/sysconfig/ config files. Before writing sysconfig files for an own RPM, I played a little bit with the zope RPM package from SuSE 8.0. I installed it, then I put a ZOPE_WEVDAV_PORT="8088" variable to the original /etc/sysconfig/zope file. BIG Problem: YaST2 shows the ZOPE_WEVDAV_PORT variable in the "etc" section of the sysconfig tree (this grafic-interface-thing of sysconfig).
I tried it with several other packages. All additional variables to sysconfig files will be put to "etc" section. What's going wrong here?
To be sure, I build a new zope RPM using the original SuSE src.rpm. I add ZOPE_WEVDAV_PORT="8088" to the SOURCE/sysconfig.zope file, built a new binary rpm and installed it. Same problme. My new ZOPE_WEVDAV_PORT is placed in "etc" section in the sysconfig tree. All other ZOPE variables are placed in right zope section. This drives me realy crazy!!!!
BTW: How do I create subfolders in the yast2 sysconfig tree?
One has to put them into /usr/share/YAST2/data/meta_sys.config too. Does anyone know how to do that in a RPM spec file? Saluti Marcus
* Marcus Schopen;
Marcus Schopen wrote:
Hi all,
One has to put them into /usr/share/YAST2/data/meta_sys.config too. Does anyone know how to do that in a RPM spec file?
define the directory for YAST2 and then add the following under your %files section could be worth a try %config %attr(-,ro,ro) %{YAST2DATA}/meta_sys_config -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
Togan Muftuoglu wrote:
One has to put them into /usr/share/YAST2/data/meta_sys.config too. Does anyone know how to do that in a RPM spec file?
define the directory for YAST2 and then add the following under your %files section could be worth a try %config %attr(-,ro,ro) %{YAST2DATA}/meta_sys_config
ahhh, great thanks. Is there more documentation for this? And I'm looking for a SuSE specific RPM Howto? Thanks Marcus
* Marcus Schopen;
One has to put them into /usr/share/YAST2/data/meta_sys.config too. Does anyone know how to do that in a RPM spec file?
define the directory for YAST2 and then add the following under your %files section could be worth a try %config %attr(-,ro,ro) %{YAST2DATA}/meta_sys_config
ahhh, great thanks. Is there more documentation for this?
Have a look at Maximum RPM book
And I'm looking for a SuSE specific RPM Howto?
Other then the one you have found I do not thinl there is one publically available -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
participants (2)
-
Marcus Schopen
-
Togan Muftuoglu