On Wed, Aug 01, 2007 at 07:14:54PM +0200, Damir Perisa wrote:
Wednesday 01 August 2007, Simo Leone wrote: | Why run checkpkg and all that garbage every | time, keep it simple and record the ones you found so whoever | upgrades it next time will have a head start and know what they're | getting themselves into.
exactly my point - i do not want to be forced to run checkpkg if i as a human being feel i do not want to for a certain update i'm _sure_ it is ok.
I'm glad that you feel it in your very soul. But a computer will be able to tell you for sure, it isn't human. While I understand your feelings, if the check wasn't as invasive as the current checkpkg (like, run on the server) wouldn't it be better to verify everything and then make exceptions for the cases you get all touchy feely about?
actually... the best way to check for so-name changes is the contact with the developement leader of a project. that's how i figure out if a pkg triggers rebuildings to other pkgs in most cases.
If they get back to you in a reasonable amount of time and remember every library that's changed between one version and another... They're also human. Jason