* Alexander Sack ([EMAIL PROTECTED]) [061222 04:57]: > On Fri, Dec 22, 2006 at 07:38:17AM +0100, Mike Hommey wrote: > > Considering how much time I've had recently, sending a patch could be > > something to help. Waiting a bit more could be something else. > > > > I *hope* to have enough time to do an upload on saturday or sunday.
> If you don't have time it would help to outline your idea about the > hackish upgrade script. Reading | Good catch. Rather than being a symlink to /usr/share/iceape/chrome, | my /usr/lib/iceape/chrome is a real directory containing a handful of | symlinks, presumably on account of having previously installed | (upgraded to) extension packages whose iceape support is somewhat off. That gives me the following idea: In case /usr/lib/iceape/chrome is a real directory, move all files therein to /usr/share/iceape/chrome, and replace the directory by a symlink (either in pre- or postinst). On the other hand, I ask myself if this bug is really RC - it only happens if a package containing that directory has been installed previously. BTW, these packages currently still contain /usr/lib/iceape/chrome in unstable: usr/lib/iceape/chrome web/iceape-browser usr/lib/iceape/chrome/checky web/mozilla-checky usr/lib/iceape/chrome/imagezoom.jar web/mozilla-imagezoom usr/lib/iceape/chrome/mozgest.jar web/mozilla-mozgest usr/lib/iceape/chrome/stumbleupon.jar web/mozilla-stumbleupon I think we should file RC-bugs against all but the first to move their file out. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]