>
>
> On Tue, Feb 03, 2004 at 11:47:56PM +0200, Aviram Jenik wrote:
> > On Tuesday 03 February 2004 22:09, Oleg Goldshmidt wrote:
> > > On Tuesday 03 February 2004 11:03, Avrahami David wrote:
> > > > Hi ,
> > > > During RPM installation I need to get some parameters from user.
> > >
> > > Interaction with user is not acceptable to RPM by design
> - it must
> > > support unattended installs/updates.
> >
> > I think David is not creating an RPM for global use, but
> rather using
> > RPM for
> > a specific use within the company, using the advantages
> that the RPM
> > infrastructure provides, while knowing for a fact the
> installation will
> > always be manual.
>
> What about using apt and other tools to automatically resolve
> the dependencies for the package?
>
> What about breaking the big package to sub-packages with
> inter-dependencies?
>
> > So whether or not that's "a good thing to do" doesn't really matter
> > here -
> > just whether or not it's possible.
>
> What happens when you need to restore the system?
>
> Another RPM rule of thumb (that the people of SuSE never heard of):
>
> Do as little as possible in the scripts.
>
> If you put too much logic in the scripts:
>
> * uninstallable RPMs (if there is an error in the pre- or preun-
> scripts)
>
> * rpm -V is nullified
>
>
> As I don't know David's exact case I can't claim any of the
> above applies there. They is just somethings to consider.
Actually I need the feature(interactive RPM) for installing our application kit on our production machines(Redhat based).
Right now it's done by regular shell script so I was thinking that RPM may be a adequate tool for wrapping those shell scripts.
I just wanted to get the RPM advantages but as I understand it's not built for such usage.
