On Wed, Feb 19, 2003, Andrews, Martin wrote:
Hi,
> Thanks for the explanation Michael. I was wondering if it was possible or
> feasible to make the user a configuration option in the rc.* file for the
> service. I guess that would be difficult if the rpm lays out the ownership
> of the data files. If I really want to go this route I might just jettison
> the rc scripts for such services and roll (reuse) my own start and stop
> scripts with my own configuration settings that place the data elsewhere.
*soapbox begin*
"The goal of OpenPKG is the creation and maintainance of portable and easy
to install software packages for use on the major Unix server platforms."
The truth behind that goal is that you can't have the advantages of OpenPKG
for free. The price to pay is to adhere to a restricting framework and to
give up some freedom and flexibility.
*soapbox end*
Now, the user _is_ already an option in the rc script that is set by
RPM during installation to match file ownerships. It might be possible
to simply override some RPM macros during installation to get file
ownerships and rc-files adapted.
But I rather doubt that this will be ever supported in OpenPKG. The
unique feature of OpenPKG of having multiple hierarchies provides a
cleaner and broader solution.
Greetings,
--
Michael van Elst
[EMAIL PROTECTED]
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
