[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: which script is missing from rpm



On Mon, Jun 08, 1998 at 03:44:18AM +0000, Robert Wilderspin wrote:
> On 5 Jun 98 03:39:03 GMT, joey@kitenet.net wrote:
> 
> >Richard E. Hawkins Esq. wrote:
> >> 
> >> Which script is it that rpm doesn't have, that dpkg does?  I had thought it 
> >> was the post-removal, but I'm being challenged on that:
> >
> >None. In fact, rpm has one script debian lacks: the verify script.
> 
> Forgive me if I'm wrong on this, because I'm only guessing here, but
> isn't that a duplicated step?  That is, given an installation and a
> configuration of a package with no errors, isn't that verified enough?
> If the verify script ever produced a different result from after the
> install/configure stages then the package is erroneous.

I would say "yes and no". Actually I don't think this is a question of
scripts really...

I do wish that dpkg had the ability to not just spit out "yes this package is 
installed" but actually verify that it is installed and notify me of
any potnetial problems with it (more thoroughly than "--audit" does
I find --audit next to useless)

The thing is dpkg has an advantage in this area...it saves a database of every 
package it encounters,l whether it is "installed" and all of the files it owns.
This is a hefty advantage. There is no NEED for a "verify" script, dpkg can do 
it in a standard way just using that database.

As I understand it if I went and did "mv /bin/ae /bin/ae-"
and had an RPM..and used verify it would tell me that the package is broken 
because /bin/ae is gone, however...I just actually did this on my debian
system and I can't even get dpkg to realize it is broken.

It would be nice if dpkg would be able to check its database against the 
filesystem when asked and see if files are missing, and warn that "Package X 
might be broken: XXX is missing" etc

If it could do this then it woul dhave IMHO a major advantage over RPM in that
one does not actually need to have the original deb to verify the package
and find problems, AFAIK to use RPM to do this you need the original RPM
(I could be wrong it has been a while since I looked at RPM)

hmm well...I have been looking for an excuse to peak at the dpkg
source code for a while now...I doubt this would be TOO hard to impliment
maybe I will have a peak (just for fun...I think my system is pretty hosed 
anyway...might as well screw around with dpkg)

-Steve

> Like I said, it's a guess.  :-)
> 
> 
> Rob Wilderspin
> --
> "But I need it to crash once every few days - 
> reboots are the only chance I get to sleep..."
> ----------------------= (send replies to rob@)
> 
> 
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: