John Dennis <jdennis@xxxxxxxxxx> writes: > On 01/06/2014 02:51 PM, Les Mikesell wrote: >> On Mon, Jan 6, 2014 at 11:38 AM, James Antill <james-yum@xxxxxxx> wrote: >>>>> Is there any sort of best practice (I'm likely missing) for >>>> accomplishing this sort of thing? I'd like to do things in a typical >>>> manner, but I'm finding yum to be somewhat prohibitive in this area. >>> >>> If you have something like database initialization, that requires >>> user interaction ... it's common to just not do it at rpm time. >> >> How is the rpm supposed to communicate to the user that those >> additional steps are needed? Or, if it set up a new user to own the >> contents, to provide the credentials to access it? > > The typical approach is to provide a setup script. The RPM does not run > the script, just installs it. You reference the script and the need to > run it in a README or INSTALL which the RPM also installs in the doc dir. Yeh, pretty much this. One additional thing that is often helpful is that if you start the daemon it errors out with "please initialize/configure me, see blah docs". -- James Antill -- james@xxxxxxx _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
