During the install of SLES7, if I remove a preselected package, for instance
libjpeg, I will get a 'Failed Dependencies' dialog which will give me the
chance to re-select it.  This dialog is an indication to me that some other
package requires libjpeg.  I need to find out what that other package is, so
that I can decide if I want to delete it or if the other package is important
enough to me where I can live with libjpeg anyway.

On Sunday 22 December 2002 03:07 pm, you wrote:
> On Sunday 22 December 2002 12:40 pm, you wrote:
> > Except this won't do what Rich wants, either.  He wants to know what
> > other packages depend on "this one."  The only way to figure that out,
> > from what I can see, is to query every single package in the RPM
> > database, and search/grep for "this one."  Now, it would probably be a
> > good idea to save the contents of that first phase so that you don't have
> > to repeat it again, since it will probably take a while.  I believe this
> > is similar to what rpmfind.net has done for various distributions, except
> > they've done it at a file level.
> >
> > But, over and above that, I think Rich is asking how to do this during an
> > install, not on a running system.  Since there is not an established RPM
> > database to query against, I can't think of any way to do that, except
> > query all the _packages_ that are on the install media (on a currently
> > running system of some kind) before starting the install.  Either way, it
> > would involve a certain amount of work, to say the least.
> >
> > Mark Post
>
> Hey Mark,
> There are --whatrequires and --whatprovides switches to the rpm command
> that will do reverse dependency searching as well. I would suggest using
> man or info to get the full documentation of what the rpm command will do.
>
> When I first read Rich's original post it looked like he wanted to search
> for installed packages and look at the dependencies of one or more of
> these, this being the case the rpm -qa | grep <whatever> and rpm -qR
> <packagename> should be sufficient. These commands wrapped up in a perl
> script could provide an interesting solution, providing there is an ongoing
> need for this type of query.
>
> Also, Rich mentions deleted packages and that should only happen post
> install. In looking at this post again, I see that he does mention that
> certain packages are de-selected and he gets dependency warnings. Once
> these warning dialogs are bypassed or satisfied, and the installation
> completes, the rpm commands will be useful in getting the information he
> wants, and with that information he can install the missing packages.
>
> Rich - sorry if I misunderstood your original post.
>
> Steve

--
Rich Smrcina
Sytek Services, Inc.
Milwaukee, WI
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Catch the WAVV!  Stay for Requirements and the Free for All!
Update your S/390 skills in 4 days for a very reasonable price.
WAVV 2003 in Winston-Salem, NC.
April 25-29, 2003
For details see http://www.wavv.org

Reply via email to