Closed Bug 265479 Opened 21 years ago Closed 21 years ago

Put browserconfig.properties somewhere else

Categories

(SeaMonkey :: Build Config, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: benjamin, Assigned: benjamin)

References

Details

(Keywords: fixed-aviary1.0, Whiteboard: [have patch] needs approval, does not block RC1 but does block localized RC2)

Attachments

(1 file)

The l10n build process doesn't know to remake browserconfig.properties. I have a better place for it, that might also make it easier to patch for distributors etc.
Attachment #162882 - Flags: review?(bugs)
Flags: blocking-aviary1.0+
Whiteboard: [have patch] need review - ben, does not block RC1 but does block localized RC2
bsmedberg, Ben is away until next week. Can you get review elsewhere?
Comment on attachment 162882 [details] [diff] [review] Move it out of a chrome JAR file Maybe, any build-fu aware person can probably review this.
Attachment #162882 - Flags: review?(bugs) → review?(bryner)
Attachment #162882 - Flags: review?(bryner) → review+
Attachment #162882 - Flags: approval-aviary?
Whiteboard: [have patch] need review - ben, does not block RC1 but does block localized RC2 → [have patch] needs approval, does not block RC1 but does block localized RC2
Comment on attachment 162882 [details] [diff] [review] Move it out of a chrome JAR file a=asa for aviary checkin.
Attachment #162882 - Flags: approval-aviary? → approval-aviary+
Fixed on branch, doesn't apply to trunk yet
Status: NEW → RESOLVED
Closed: 21 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
Depends on: 265812
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: