Why do we get these decompression problems anyways? I've seen it with 
pkunzip, WinZip and whatever 'unzip' comes with Slackware7....

What I do is unzip to C:\Program Files\Mozilla-win32\ (after deleting 
all contents)
and mozilla stores my user data elsewhere (f:\home\myke\mozconf\{stupid 
salting....}\*)

(I Hate salting...  Is there a way to do away with it that I've missed? 
(short of recompiling?))

This works for me - Or - at least it keeps my user data intact, plugins, 
chromes & skins ... are nuked.


#!/bin/sh
cd /tmp
/usr/bin/wget 
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32.zip
rm -rf /vols/next/c/Program\ Files/mozilla-win32/bin/*
cd /vols/next/c/Program\ Files/mozilla-win32/
/usr/bin/unzip -o -C -u /tmp/mozilla-win32.zip
mv /tmp/mozilla-win32.zip /vols/local/home/downloads/network/

(/vols/next is an NFS mount to my Win2KP desktop machine)

Mike (at/dot) Geiger (dot) ca


Patrick Gallagher wrote:

> Chuck Coulson wrote:
>
>> What's the best way to install new nightly builds?  If I replace the 
>> old folder with the new build, I lose plugins, etc.  Thanks.
>>
>> Chuck Coulson
>>
>
> I've found the best way to keep nightlies up to date is to maintain a 
> Netscape 4.7x installation with the same preferences, etc. - When you 
> decide to upgrade, make sure the bookmarks, newsgroups, mail, address 
> books in 4.7 are up to date, delete your moz profile, uninstall moz, 
> delete the moz folder, and install the new nightly - the new nightly 
> will migrate the NS 4.7 folder automatically. While this would involve 
> using 4.7 frequently to keep mail/news/etc. up to date, it's very 
> effective - move your plugins folder out, and back in when you're done :)
>
> The other option is to just continually upgrade over moz - which 
> retains all plugins and settings, but sometimes files don't get 
> overwritten properly and the way profiles and variables are read can 
> change in different builds, so unfortunately that could lead to nasty 
> buglike behaviour where the problem is actually an improper 
> installation, as opposed to a problem with the files related to that 
> build. I frequently use this method, but if something starts acting 
> up, I reinstall using the uninstall and migrate method, and most of 
> the problems clear up :)
>
> Patrick



Reply via email to