Did not mean to ruffle any feathers. I am probably not the most common openpkg user - I know that. I was just describing my thinking in case others were interested. The way openpkg currently works is fine. If I want to use alternate users I can do so and simply use openpkg as a vehicle for distributing the binaries and not use the rc system it provides. I am fine with that. In simple cases openpkg will still provide a quick and easy way to get the service running too.
As an aside - I see multiple hierarchies a heavy solution. Building the bootstrap openpkg rpm itself is quite time consuming. Personally, I would not want to have to maintain that for every service I run. But hey - as Larry Wall says - there's more than one way to do it. Martin > -----Original Message----- > From: Michael van Elst [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 19, 2003 8:07 AM > To: [EMAIL PROTECTED] > Subject: Re: rc does not return failed exit status? > > > 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] > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
