On 27 Jun 2002, seth vidal wrote:
> I think the general rule to follow should be:
>
>
> if we can't get to any server/mirror in a single server section we exit
> w/error
> if we can't get a headers.info file for any server-section we exit
> w/error
> if we can't get a header that the headers.info file claims exist we exit
> w/error.
> if we can't get an rpm that the headers.info file claims exist we exit
> w/error.
> if we get an rpm that fails the gpg/md5 check we exit w/error.
>
>
> in general I want the default case to be "do nothing but tell you about
> it" rather than "try our best to continue despite the servers spewing
> lies and filth".
>
> It might cause more work for a user but I tend to the "don't break
> stuff" camp when it comes to installing things.
This is consistent with what I was suggesting, except that when running
yum interactively (the state where it asks questions like: "Do you like
this list of files and should I proceed?") one could conceivably insert
messages like "I can't find these two rpm's, but nothing else depends on
them -- do you want to proceed anyway and find the missing rpm's on your
own?" with a y/n answer.
When running non-interactively I totally agree -- punt with as detailed
an error message as you can stand to arrange.
rgb
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
