Closed
Bug 179565
Opened 22 years ago
Closed 22 years ago
configure and milestone.txt have an inconsistent milestone.
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.3alpha
People
(Reporter: mozilla-bugs, Assigned: netscape)
Details
Attachments
(1 file)
2.42 KB,
patch
|
asasaki
:
review+
asasaki
:
review+
|
Details | Diff | Splinter Review |
I did
egrep -r '1\.(2b|3a)'
in Mozilla sources (checked out of CVS around 2002111023 - e.g. 12 hours ago)
and found some weird results.
1) Really annoying:
> configure:MOZILLA_VERSION='1.2b'
> configure.in:MOZILLA_VERSION='1.2b'
> config/milestone.txt:1.3a
This IMHO is pretty bad. In particular, this way we build Mozilla that calls
itself 1.3a, but is installed into .../lib/mozilla-1.2b! Shouldn't configure
take the version off milestone.txt for consistency?
2) A few others that can be potentially inconsistent (not sure):
> xpinstall/packager/win_mfcembed/runapp.bat:set GRE_VERSION=1.3a
> embedding/qa/testembed/winEmbedFileLocProvider.cpp: strcpy(szKey,
"Software\\Mozilla\\GRE\\1.2b");
> /embedding/tests/mfcembed/winEmbedFileLocProvider.cpp: strcpy(szKey,
"Software\\mozilla.org\\GRE\\1.3a");
and
> xpinstall/wizard/mac/rsrc/MacInstallerVersion.r: "1.2b",
// short version string
> xpinstall/wizard/mac/rsrc/MacInstallerVersion.r: "Mozilla 1.2b
Installer" // long version string
> xpinstall/wizard/os2/builder/build.pl:$verPartial = "1.2b.0.";
> xpinstall/wizard/windows/builder/build_gre.pl:$verPartial = "1.3a.0.";
Comment 1•22 years ago
|
||
I wasn't even aware there was a version number in configure. When did that
happen? Who usually updates it?
We're still in the process of updating other versions in the tree to 1.3a so
those other files should be changed over the coming week as r/sr/a comes in.
Kyle's tracking those changes.
Target Milestone: --- → mozilla1.3alpha
Assignee | ||
Comment 2•22 years ago
|
||
The configure.in's milestone variable predated milestone.txt by quite a bit. We
have discussed pulling the info from milestone.txt once it became the standard
but we haven't gotten around to it.
Comment 3•22 years ago
|
||
i've gotta change commercial milestone.txt to allow for multiple settings
anyway. should i just change milestone.txt to be a sourceable bourne shell
script which my perl module can parse and configure can '.'?
Assignee | ||
Comment 4•22 years ago
|
||
That's not necessary. We can just assign the MOZILLA_VERSION variable in
config.mk using the perl script.
Assignee | ||
Comment 5•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Attachment #106541 -
Flags: review?(asasaki)
Updated•22 years ago
|
Attachment #106541 -
Flags: review?(asasaki)
Attachment #106541 -
Flags: review+
Assignee | ||
Comment 6•22 years ago
|
||
Patch has been checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•