Closed Bug 71465 Opened 25 years ago Closed 24 years ago

nsDirectoryService should support "Essential Files"

Categories

(Core :: XPCOM, defect, P2)

PowerPC
All
defect

Tracking

()

RESOLVED WONTFIX
mozilla1.2alpha

People

(Reporter: bnesse, Assigned: sdagley)

Details

(Keywords: l12y)

There are currently a couple of places in the codebase with code similar to: rv = NE_GetSpecialDirectory(NS_XPCOM_CURRENT_PROCESS_DIR, aFile); #ifdef XP_MAC aFile->Append("Essential Files"); #endif This is a hack and is totally non-localizable. One potential method for fixing this would be to add a Mac specific property to nsDirectoryService which would return a pointer to the appropriate place, giving us code more like: #ifdef XP_MAC rv = NE_GetSpecialDirectory(NS_XPCOM_ESSENTIAL_FILES_DIR, aFile); #else rv = NE_GetSpecialDirectory(NS_XPCOM_CURRENT_PROCESS_DIR, aFile); #endif
Keywords: l12y
Adding Conrad to the cc: list
I agree. And it's easy enough. It should be XP so that the #ifdef is not needed. Essentially, that dir is the "DLLs linked by the OS" dir. On other platforms, it is the same as the bin dir. BTW - what code is looking for that location? Should it be in the first place?
Yeah, an XP define would be even better if it did the right thing. The preferences code is looking there for preferences file(s), and the "ScriptSecurityManager" looks like it is looking for certificates there. The installer also references the directory, but it doesn't seem to be doing it in the same way...
> The preferences code is looking there for preferences file(s) Is this right? Why would it be looking there? I'll have to check this out > the "ScriptSecurityManager" looks like it is looking for certificates there. Hmm, I'll have to look at this. It seems wrong. It seems that these files should be on a per user basis in NS_APP_USER_PROFILE_50_DIR, and if these files are indeed global to all users they should be in NS_APP_APPLICATION_REGISTRY_DIR > The installer also references the directory This seems like about the only thing that should be looking there.
>> The preferences code is looking there for preferences file(s) > Is this right? Why would it be looking there? I'll have to check this out Actually it is looking for the "netscape.cfg" or "Mozilla.cfg" file here, not just any old prefs file.
Target Milestone: --- → mozilla0.9
Target Milestone: mozilla0.9 → mozilla0.9.1
Setting target milestone to 0.9.2 (check it in anytime, even before, when the tree is open for). Per PDT triage.
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Moving to P2, 0.9.3.
Priority: -- → P2
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Keywords: nsBranch
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Marking nsbranch- as it was decided in the August bug triage that we wouldn't have enough time in eMojo to fix this. Let's revisit for MachV.
Keywords: nsbranch-
removed keyword nsbranch since it now has nsbranch-, per pdt mtg.
Keywords: nsbranch
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Blocks: 107067
Keywords: nsbranch-
cc. yxia
Is there any reason to localize this folder name? If so, we may have more this kind of stuff, like: #define SEARCH_DIR_NAME "Search Plugins"
No relavent activity in this bug since it was targeted at 096. Resetting target milestone, please update it when you get back to this bug.
Target Milestone: mozilla0.9.6 → ---
I just wondering if it's valid l12y bug or not. Our l10n group is reviewing all l12y bugs.
Ying-Lin, Um, what does l12y mean? And any decision on if this is a l12y issue? And is the "Essential Files" folder name ever localized? I'm guessing it's not since we have it hardcoded (as well as the "Components" folder name)
Target Milestone: --- → mozilla0.9.9
l12y=localizability, for this folder name, we never localize it before, and I don't see any reason to localize this folder name from localization point.
Doh! I guessed that but mistakenly counted the l and y coming up with 14 characters. Thanks for the word on the non-l10n for that folder.
No longer blocks: 107067
Keywords: nsbeta1
nsbeta1-, per ADT triage team
Keywords: nsbeta1 → nsbeta1-
Since this directory is never localized moving out past 1.0
Target Milestone: mozilla0.9.9 → mozilla1.1
Putting on Mozilla1.2 radar since I was wandering around in the nsDirectoryService code while looking at a Chimera bug and it reminded me I had this bug in my future list
Status: NEW → ASSIGNED
Target Milestone: mozilla1.1alpha → mozilla1.2alpha
With OS 9 going away, and the OS X build being packaged, I'm wondering if we shouldn't just eliminate "Essential Files" and let the OS X build be the same as Windows/Linux.
> With OS 9 going away, and the OS X build being packaged I like that idea. The additional problem with "Essential Files" is that it requires an alias to the "Essential Files" dir be present in the 'cfrg' resource. It's another one of those annoying little details an app has to deal with when embedding us. If shared libs are in the same dir as the app, that wouldn't be needed :-)
WONTFIX per Brian & Conrad's feedback
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
See! Proof that if you wait long enough any bug will work itself out. :) Me thinks that a new bug may be in order... "Remove support for Essential Files folder from non-Carbon builds"
er, make that "from carbon builds"...
You need to log in before you can comment on or make changes to this bug.