MSlinux? (Score 1)

When I mention a RPM screwing up your system, I mean an RPM messing up the packaging system. Like a partially installed RPM that fond a little bug that makes it abort,...

Well, all I can say is that any program may have bugs, and RPM is no exception. Presumably, you've reported any bugs you've found and they've been fixed.

I don't have enough experience with periphery RPM tools to provide any suggestions for dealing with a corrupt RPM database.

And how do I, after installing with "make install" say the new GTK libraries, then without forcing it installation install Gimp?

Not having installed either of these packages, I can only assume you mean, "...then without forcing it ... install Gimp [from the RPM]?" Well, you can't install Gimp from the RPM without forcing it (using rpm --nodeps) because RPM, by the very nature of a package manager, is attempting to prevent you from inadvertently installing something without its prerequisites. RPM doesn't presume to guess about what it doesn't know. It doesn't know you have gtk installed because you didn't install it with RPM (and thus, the information isn't in the RPM database).