Closed Bug 136690 Opened 23 years ago Closed 22 years ago

inconsistency in the fileversion info

Categories

(SeaMonkey :: Build Config, defect, P4)

x86
Windows 2000

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: bugzilla, Assigned: asasaki)

References

Details

the new version information in the file properties is inconsistent with the old stuff found in some other files: check the new fileversioninfo in fx "jpeg3250.dll" and compare it to fileversioninfo found in "npnul32.dll" or "SETUP.EXE"
-> aki
Assignee: seawood → asasaki
i can't seem to find the jpeg3250.dll file, but I'm guessing that the one that doesn't say 0.0.0.0 has a RESFILE declared in makefile.win and/or Makefile.in... RESFILE will override the auto-version stuff.
Status: NEW → ASSIGNED
in inconsistency is because the versioninfo of fx npnul32.dll is defined in: http://lxr.mozilla.org/seamonkey/source/modules/plugin/samples/default/windows/npnul32.rc#75 all the other dll's get theire versioninfo from the perl script
Severity: normal → minor
Priority: -- → P4
Target Milestone: --- → mozilla1.2beta
adding cc's
ok. the fix is simple: cvs rm the .rc file, and remove the RESFILE line in the makefiles. however, *whether* we want to do this isn't certain... perhaps there's a reason why we're versioning these with specific version numbers.
um...plugins need that rc file for meta data.
so the autoversion .rc file won't do? if so, then we need to keep it there and mark this won'tfix. also need to check on setup.exe's .rc file.
The version info is probably not important to us but we NEED the other data in the rc file. Is the script capable of merging rc files?
yes... i'll submit a patch.
Blocks: 169074
No longer blocks: 169074
Depends on: 169074
Target Milestone: mozilla1.2beta → mozilla1.3alpha
Target Milestone: mozilla1.3alpha → Future
engineer gone, wontfix. reopen and reassign to yourself if this is something you want to do.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.