Closed
Bug 244558
Opened 21 years ago
Closed 20 years ago
cookperm.txt -> hostperm.1
Categories
(Core Graveyard :: Profile: Roaming, defect)
Core Graveyard
Profile: Roaming
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: BenB, Assigned: BenB)
Details
Attachments
(1 file)
2.11 KB,
patch
|
dwitte
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
Comment 1•21 years ago
|
||
mvl, wanna take this?
Comment 2•21 years ago
|
||
Assignee | ||
Comment 3•21 years ago
|
||
> (also, how do you propose to keep the filenames in your
> new code synchronized with changes to other respective modules, such as has
> happened here?)
I don't expect profile filenames to change ;-)
Thanks for taking this. Should be trivial. grep finds appearances in files.xul
and filedescr.properties.
Assignee | ||
Comment 4•21 years ago
|
||
r=BenB for the patch :)
(my tree is still updating)
Assignee | ||
Comment 5•21 years ago
|
||
cert7.db changed to cert8.db, too.
Assignee | ||
Comment 6•21 years ago
|
||
Filename changes may cause dataloss in edge cases, e.g. when you upgrade, but
your local profile is not the latest one (or - even worse - fresh) when you run
the new build the first time. Building explicit support for profile file name
changes into roaming would complicate the code. Just supporting multiple
filenames per item would make sense, but would cause strange effects
(transferring both versions forever, spurious files for new profiles).
Assignee | ||
Comment 7•21 years ago
|
||
Patch for both files.
I didn't change the description "Cookie Permissions", assuming that it contains
only cookie and image permissions and image permissions are unimportant in
comparison. If other types of data exist there (e.g. popup blocking), we'd need
to change the description.
Assignee | ||
Updated•21 years ago
|
Attachment #149250 -
Flags: review?(dwitte)
Assignee | ||
Comment 9•21 years ago
|
||
ccing some crypto guys. I don't think that filename changes are a good
versioning strategy, at least for the browser. But I don't have a better suggestion.
Assignee | ||
Comment 10•21 years ago
|
||
*** Bug 244793 has been marked as a duplicate of this bug. ***
Comment 11•21 years ago
|
||
Ben, since you added me to the CC list, would you care to explain what
you're trying to do, and why, and what question you have for me about it?
Thanks.
Assignee | ||
Comment 12•21 years ago
|
||
dwitte: ping?
Nelson, see comment 9. It seems NSS changes the filename (in the profile) of
certdb whenever you have a format change. I'd prefer, if it didn't, because it
will cause problems for roaming (as described in this bug, esp. comment 6), and
I don't think it's a good idea in general, no other critical files there do
that. I just wanted to point out the problem to you. If there's need for
discussion, we can move to npm.crypto and/or .prefs.
Assignee | ||
Updated•21 years ago
|
Attachment #149250 -
Flags: superreview?(jag)
Attachment #149250 -
Flags: review?(pete.zha)
Attachment #149250 -
Flags: review?(dwitte)
Comment 13•21 years ago
|
||
Comment on attachment 149250 [details] [diff] [review]
v1
sorry for the delay. instead of "cookie permissions" you may want to call it
"host permissions", hence the new filename, but that's up to you since it's
your module. ;)
r=dwitte
Attachment #149250 -
Flags: review?(pete.zha) → review+
Comment 14•21 years ago
|
||
Any chance we could get this one into the tree?
the file should be called "Cookie/Image permission" or just "Permission File"
like it says in the file itself.
Component: Profile: BackEnd → Profile: Roaming
QA Contact: core.profile-manager-backend → core.profile-roaming
Summary: [Roaming] cookperm.txt -> hostperm.1 → cookperm.txt -> hostperm.1
Comment 15•21 years ago
|
||
you might want to try alecf for sr here...
Updated•21 years ago
|
Attachment #149250 -
Flags: superreview?(jag) → superreview?(alecf)
Attachment #149250 -
Flags: superreview?(alecf) → superreview+
Comment 16•20 years ago
|
||
Ben, shall we check in this patch since it has got r= and sr= already
Comment 17•20 years ago
|
||
Ben: could you please do the checkin
Comment 18•20 years ago
|
||
just checked in
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•20 years ago
|
No longer blocks: roamingtracking
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•