On Fri, Sep 20, 2002 at 11:22:10AM +1000, Mike MacCana wrote: > RPMs are supposed to be non interactive. This allows you to, say, > install a couple of hundred packages in an automated fashion from a > scheduler like cron. > > If your application needs some inital setup, you should put the script > or application which does this as another SOURCE in your spec, give it > an obvious name, and mention it in your documentation.
yeah we do something similar for other rpms (wrap it with an install script, license agreement etc then tar up the lot, which I think is a pest cos it means you have to untar it and run the install script rather than just deal with a single rpm). So the non-interactive rule can't be turned off somewhere? I can see the benefits of non-interactive installs but this rpm is going to be a fairly limited release. Sounds like another limitation of the rpm format. Dave. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
