But lets get to basics. You complain because it wouldn’t stop you. That’s the problem. Software is only as good as the user. You chose to check things manually thinking that you could do better than the automatic checking. It’s possible. But after all the problems you had, it still asks one final time if you want to proceed. You said yes. Yast didn’t say yes, you did. It’s that final click that did it. You could have aborted and tried a different approach. Now you blame Yast for allowing this.

It’s the old blame game. You chose to blame the product thinking that you can’t do anything wrong. Oh, well, I guess it’s Yast’s fault for not stopping you. I hope you get it fixed without losing your data. Hopefully you had it on a separate partition.

Mike

Either way, It was your choice to continue. You had the final say. Once you ignored all the cautions, like the dependencies, and clicking through all the cancels, you continued on.

Yes, I understand that this was a rant. But I’ll say it again. It wasn’t Yast that made the final decision to do this. You made that final click.

Centerlink’s reply:

Mike,

You haven’t used YaST yourself. When I turned off the automatic dependency checking, it does not mean that I discarded the dependency checking of the packages. It means only that I did it manually. It was not possible to continue without handling of dependencies. Dependency checking means that YaST will check which version of some other packages and libraries are needed for a specific package (to work). You can also select to ignore dependency checking warnings for a specific package. For the most packages it does not mean that the whole installation will be corrupted. For example, you can install some library package from the source. But Yast doesn’t always know that that package already exists, and creates a false warning during the dependency checking.

It’s not about the software. He already knew he only had 3% of the drive left. The OP stated that. I’m sorry, but it’d kinda like passing a cop when you are doing 100 mph in a 30 mph zone. You know it wrong, but hey, the car will go that fast, so why can’t I do it?

Why is it that folks absolutely have to have something or someone else to blame? Oh, it’s the software that allowed me to do it. Or some other silly reason for their own problem. It’s not the fault of the software. I guess it’s the same as blaming the auto maker for building a car that goes too fast and you get pulled over. “No officer, it’s not my fault, send the ticket to the maker of the car because it allowed me to go too fast”. That’s would really go over well. You might try it though, you might get a cop with a sense of humor and let you off with just a warning.

OH, and just for the record, after clicking all those cancels, it still gives you one more try to abort the install. Are you sure? Apply or abort. With all the problems it was showing, somehow I think I would have aborted. But that’s just me. I tend not to try things when it doesn’t look right.

Mike

Centerlink’s reply:

Mike R.

Your analogy is not quite correct. I’ll try the better one:

Let’s image that you are a tipper truck driver. Your truck is loaded by a hydraulic shovel driver. But because of rainy last night and moist sand your truck will be overloaded. On your way an officer called YaST stops you and tries to calculate, if your truck is overloaded. But he fails. Some truck drivers have told me, that cops can sometimes fail with these kind of calculations. And after the next turn you will continue towards a weight-limited bridge…

Sure we know the size of the package prior to its installation, but this is not enough information. A package contains files which might go anywhere in the filesystem, some to /usr, some to /var etc,

There is no way to know how much space is occupied on each partition on the disk, especially as the complete filelists of packages are not downloaded to save download & repository refresh time.

Centerlink’s reply (for other morons ):
http://en.wikipedia.org/wiki/PEBKAC

PLS, tell me something. Have you ever used Windows? Do you have updated any software or upgraded the operation system? Have you ever have computer with two partitions, C and D ? Have you ever run out of the C partition space? It happens sometimes. I have seen it happen and not only for my computer. The latest was last summer. I had to start to work with such kind of PC (the previous user of that PC had a vacation in New York and I could not re-install Windows before his return). How does Windows setup behave when there is not enough space on C partition? The answer is: It always tells about it. It tells how to solve the problem. And it quits. It never has allowed me to continue. But OpenSUSE 10.3 YaST allows it.

Centerlink’s reply:
Linuxtoday’s comments show that there is at least two paradigms for software testing. According to one paradigm software designers should first think how to test each piece of sofware. When they know how to test it, they can design the functionality to be tested. According to another paradigm it is wrong. A designer can never image, how other designers/users can use any piece of software. Therefore, only other designers and users can design test cases and do testing. But those software designers who advocate the first paradigm, get quite angry, when other persons use their software or any software by other way. My guess is that Mike R. and others are software designers.

Centerlink’s reply:
Yes, I agree. I have used SuSE since release 6.4. But it will never be the best distro if there aren’t morons, who try out every aspect of the distro.

Centerlink’s reply:
I knew it prior to my upgrade. But there are many newbies, who don’t check it. They have to rely on it what YaST tells them.

Centerlink’s reply:
It is a long way to really user-friendliness when upgrading and installing Linux Distros.