On Mon, 8 Mar 2004, Matthew Miller wrote: > On Mon, Mar 08, 2004 at 08:14:34AM -0800, Baz wrote: > > 1. How can one install a rpm package and would like to change and set some > > values such as "servername"? Only by prompting users during postinstall > > process? Please enlight me in details. I am surprised that there are nobody > > doing it in rpm... > > No, you can't prompt during the postinstall. Preconfigure the package with a > sensible default for the intended platform. If that's not good enough, > either prompt for the correct info the first time the program is run (if > it's an interactive app) or else simply don't start until properly > configured (if it's a server). > > > 2. If so, then is there a way to do it silently just like what I have > > described? One command with additional strings and pass those strings into > > the postinstall process? e.g. "rpm -i software_a.rpm STRING1 STRING2"??? > > 3. Can this: "rpm -i software_a.rpm STRING1 STRING2" be done? > > > Errr... is the plan here to repeat yourself until someone tells you what you > want to hear? Appearantly so (-; > How would yum or apt or anaconda know what packages need what > strings passed? You said that yourself, sane defaults. Also, his packages may not be intended for anaconda, yum or whatever. Lastly, solaris packages allow support for a an admin script which simply lists the responses for package questions in order; in other words querying from packages has been supported on other platforms, without loss of automatability. Furthermore, the mechanisms for automating these packages are not limited to the way Solaris did it. That being said, its not my number one feature wanted. > If you're installing multiple packages, how would rpm know > which STRING goes with what package -- or that STRING isn't a package name > itself? Again, this is doable, its just not done. If for instance scriplets where evaluated at run time, the name spacing you suggest would be needed is not necessarily required, because packages can name mangle there macros they wish to use if they wish (i.e. _my_package_hostname), but in some cases you might want it across multiple packages (though some form of name mangling might still be a good idea). As far as actually delivering a var to specific package, this could be done too. Once the evaluating of scriplets at install time is implemented, implementing a per pkg set of macros would not be too hard from the api...from the CLI, now that could get challenging. Again, though, I would put that lower in the priority bucket. Cheers...james > > > _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
