nsProfileLock needs to be factored out of nsProfileAccess

RESOLVED INCOMPLETE

Status

Core Graveyard
Profile: BackEnd
RESOLVED INCOMPLETE
15 years ago
2 years ago

People

(Reporter: Conrad Carlen (not reading bugmail), Assigned: Conrad Carlen (not reading bugmail))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

15 years ago
Two reasons:
(1) The profile dirserviceprovider needs locking when used without profile mgr.
(2) The cache needs to lock its directory when its directory is not within the
profile dir.

As far as module dependencies, we don't want cache to depend on profile. I'd
like to divide the profile stuff into "profiledir" and "profilemgr" The first
would be just for things which use profile-relative data and the 2nd would be
for all the other profile manager stuff.

BTW, I've already done this on a branch for profile sharing - it just needs to
be brought to the trunk.
(Assignee)

Updated

15 years ago
Blocks: 197904
QA Contact: agracebush → profile-manager-backend

Comment 1

2 years ago
This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE.

If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.
No longer blocks: 1243899
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.