8019 - Create profile needs to copy contents from Defaults folder

Status: VERIFIED FIXED

(Core Graveyard :: Profile: BackEnd, defect, P3)

Description

[selmer (gone)]

For parity with 4.x, the profile creator must copy the contents from the
application's Defaults folder into every new profile.

Comment 1

[Chris Waterson]

So what's the status on this bug? Will it be fixed for M8? I am trying to get
7921 done.

Comment 2

[gayatrib]

Checked in the code to support the above. Here is the list of locations for the
defaults folder on the different platforms.

Win : \dist\ProfileDefaults
Mac : :Documents:Mozilla:ProfileDefaults
Unix : ~/.mozilla/ProfileDefaults
BeOS : mozilla/ProfileDefaults

Comment 3

[selmer (gone)]

Is there a compelling reason why we're not using the same defaults folder we've
used in every previous release?

Comment 4

[racham]

The only reason (for not using name Defaults) is that the name Defaults is very
close the folder name Default which gets created when user chooses to create
profile named "default", i.e., a case where user does not override the default
profiole name "default". Though on Windows and Mac the Defaults (i.e.,
ProfileDefaults) folder lives one level above the profile directories, on Unx
and BeOS, the directory lives along with the profile directories. So to avoid
confusion (while maintaining the same name across all platforms), name
ProfileDefaults is picked.

Comment 5

[leger]

Clearing Fixed resolution since this has been Re-opened.

Comment 6

[Grace Bush]

I can see the ProfileDefaults folder being created - but no information is being
stored-what should go there? data saved between builds? bookmarks--per 7921?

Comment 7

[selmer (gone)]

After talking to Bhuvan, it appears that the conflict with the name "Defaults"
is from the concept of putting this folder in with the profiles of a particular
user on Unix machines.  This concept is incorrect.  The Defaults folder is a
mechanism for distributors to change the default content of newly created
profiles and is not tied to a particular user as suggested.  In any case, where
would the content in the user directory come from?

For this to work properly, the Defaults folder needs to be created and filled by
the installer and then copied into every new profile as it's created by the
app.  For our internal usage, it's OK to check in a Defaults folder that lives
in the dist with the executable and put content in it to help people test
things.  This should probably live in the mozilla/profile directory in CVS and
it should have a makefile to move everything into the right place in the dist.

Comment 8

[racham]

A directory named "defaults" is added to mozilla/profile. All the defaults files
that need to go into the directory of newly created profile live under this
folder. At present, only bookmarks.html exists in that folder. Makefiles in that
folder should be updated whenever a new file is added to that ("defaults")
directory. In the build process, files in the "defaults" folder gets copied to
the following destinations on different platforms.

Windows : <install directory>/defaults
Unix    : <install directory>/defaults
Mac     : <install directory>:Defaults

When a new profile is created, all the files in the above folder gets copied
into that profile directory.

Comment 9

[Grace Bush]

Linux:
ftp://sweetlou/products/client/seamonkey/linux_glibc/2.0/x86/1999-07-08-18-M8

Mac:
ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/1999-07-08-18-M8

Windows:
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-07-08-19-M8

Comment 10

[leger]

Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.