Well, what works *really* well is:
- get installer for firefox
- install with installer
- download moox build
- zip firefox directory (usually c:\program files\firefox or something)
- DELETE firefox directory
- unpack moox build (in this case to c:\program files)
- OPTIONAL: if original firefox directory was NOT named "firefox" rename the unpacked directory
this works perfectly for me. DON'T simply unpack a moox build over an already existing firefox directory!! this WILL lead to problems. (as I found out). and if the newer build is too unstable (happens from time to time) simply delete the directory and unzip the original one again.
hth.
maybe stupid question: difference between branch and trunk?
-
- Posts: 1328
- Joined: September 28th, 2003, 8:58 am
- Contact:
- Powersurge
- Posts: 20
- Joined: August 18th, 2004, 1:34 am
- Location: Germany
- Contact:
Something else, but related; this might be a good thread to ask this: What's actually gonna happen to Firefox once it lands on the trunk ? What will be done code-wise ? In which way will what we see in the nightlies change ? Will it stay with the trunk for a while, or is it expected to branch off again soon for a 1.1 (1.2 .... 1.5 .... whatever) release ?
Firefox. To burn or not to be.
-
- Posts: 384
- Joined: September 26th, 2004, 2:11 pm
- Location: Essex, UK
-
- Posts: 2417
- Joined: November 4th, 2002, 4:47 pm
- Location: London, UK
- Contact:
chrisblore wrote:Will it stay with the trunk for a while, or is it expected to branch off again soon for a 1.1 (1.2 .... 1.5 .... whatever) release ?
From what I understand the 1.1 release will be from the trunk and will be mainly a 'clear-up' release with fixes incorporated from the Aviary branch and the trunk.
I think it's unlikely that they'd actually release directly from the trunk. I would imagine they'll either use the 1.8 branch when that happens, or they'll make a special branch for Firefox 1.1 from the trunk. But the idea is to be back on the trunk for a while in order to do the merging and fix ups, and I imagine that the branch would be a much shorter term thing, like previous branches, rather than a long parallel effort like the aviary branch.
-
- Posts: 384
- Joined: September 26th, 2004, 2:11 pm
- Location: Essex, UK
That would probably make more sense on reflection because development could then be continued more easily on the trunk without closing the entire tree every five minutes in anticipation of the 1.1 release.michaell wrote:chrisblore wrote:Will it stay with the trunk for a while, or is it expected to branch off again soon for a 1.1 (1.2 .... 1.5 .... whatever) release ?
From what I understand the 1.1 release will be from the trunk and will be mainly a 'clear-up' release with fixes incorporated from the Aviary branch and the trunk.
I think it's unlikely that they'd actually release directly from the trunk. I would imagine they'll either use the 1.8 branch when that happens, or they'll make a special branch for Firefox 1.1 from the trunk. But the idea is to be back on the trunk for a while in order to do the merging and fix ups, and I imagine that the branch would be a much shorter term thing, like previous branches, rather than a long parallel effort like the aviary branch.
- Powersurge
- Posts: 20
- Joined: August 18th, 2004, 1:34 am
- Location: Germany
- Contact: