> 
> There is another practice which is far from "best". It's only  
> slightly less evil than modifying other packages. It causes headaches  
> in the long run. It depends on the Monticello and PackageInfo  
> version. You should not use it but stick to the best practice. And  
> definitely do not use it for anything you want to share. You have  
> been warned. This practice is called "overrides", and works by moving  
> your method into a "*mymodule-override" category. This lets  
> Monticello know this is a temporary override and it will try to  
> restore the original method when you remove it from your package - it  
> relies on a proper version history in the changes file for that. This  
> is highly unreliable in most but the very simplest cases. Did I  
> mention you should not use it, unless you *really* know what you're  
> doing? And don't come back and complain ;)
> 
Oh, well, I can read between the lines that this is a good approach
to do :) All I can understand is that in my case it only can do
less harmful changes. I haven't tried but it looks like _exactly_
what I was looking for. And I will convince a lot of other people
to use it, too. :))

thanks,

Norbert