Closed Bug 299149 Opened 20 years ago Closed 18 years ago

On first launch from a tree, files in browser/locales are overwritten

Categories

(Firefox Build System :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla3 alpha1

People

(Reporter: asaf, Assigned: vlad)

Details

(Keywords: dogfood, regression)

Attachments

(1 file)

After first lauch of ff from my tree, i get these changes
http://mano.fastmail.fm/browser_locales.diff
into the tree itself.

This is a recent regression (~month, i think).
I can confirm seeing something similar, although I can't reproduce it right now.
What does your profile/mimetypes.rdf look like? Is it symlinked somewhere, or
hardlinked?
Flags: blocking1.8b3+
Well, the three files in Mano's patch are all symlinked in
dist/Firefox.app/Contents/MacOS/defaults/profile to the originial source file. 
I just tried creating a new profile, and it properly copies the files (such that
there are no symlinks in the profile directory).  The only thing I can think of
is that at some point this was broken and it was symlinking files within the
profile.
linked to browser/locales/en-US/profile/mac/mimeTypes.rdf
I understand that dist/DeerPark.app/Content/MacOS/defaults/profile/mimeTypes.rdf
is symlinked into the source tree: that behavior is by design.

The bad part is having either of those things linked to the profile at all.
FYI, I get the same results with a new profile created by the same build.
closing down for 1.8b3, let's try and get this in for 1.8b4.
Flags: blocking1.8b4+
Flags: blocking1.8b3-
Flags: blocking1.8b3+
closing down for 1.8b3, let's try and get this in for 1.8b4. 
Flags: blocking1.8b4+
Flags: blocking1.8b4+
Flags: blocking1.8b4+ → blocking1.8b4-
Flags: blocking1.9a1?
I guess this doesn't happen on other platforms?
Flags: blocking1.9?
(In reply to comment #9)
> I guess this doesn't happen on other platforms?

Right: everybody else can run directly from their obj dir, Mac needs to make -C browser/installer and then run from the .dmg to keep from messing up the source dir.
I had a profile that got these symlinks, and then when I removed the tree, I ran into problems.  Specifically, I couldn't add any bookmarks.

see bug #354245.

lrwxrwxrwx    1 sspitzer  sspitzer       85 Jun 15 15:43 localstore.rdf ->
/Users/sspitzer/Desktop/bonecho2/mozilla/browser/locales/en-US/profile/localstore.rdf
lrwxrwxrwx    1 sspitzer  sspitzer       88 Jun 15 15:43 mimeTypes.rdf ->
/Users/sspitzer/Desktop/bonecho2/mozilla/browser/locales/en-US/profile/mac/mimeTypes.rdf
-rw-r--r--    1 sspitzer  sspitzer    26946 Sep 25 19:38 prefs.js
lrwxrwxrwx    1 sspitzer  sspitzer       81 Jun 15 15:43 search.rdf ->
/Users/sspitzer/Desktop/bonecho2/mozilla/browser/locales/en-US/profile/search.rdf
FWIW, the workaround is to create the profile from a release build (or another tree).
use SYSINSTALL instead of INSTALL, per bsmedberg's suggestion, to copy the profile files in to the install dir instead of symlinking.  The (much harder) real fix is to have the profile instantiation goop dereference symlinks.
Assignee: nobody → vladimir
Status: NEW → ASSIGNED
Attachment #246196 - Flags: review?(benjamin)
Attachment #246196 - Flags: review?(benjamin) → review+
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Flags: blocking1.9a1?
Flags: blocking1.8b5-
Flags: blocking1.8b3-
Target Milestone: --- → Firefox 3 alpha1
Component: Build Config → General
Product: Firefox → Firefox Build System
Keywords: dogfood, regression
Target Milestone: Firefox 3 alpha1 → mozilla3 alpha1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: