Closed
Bug 50627
Opened 25 years ago
Closed 22 years ago
Binaries on Windows platform do not have version resources
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
mozilla1.0
People
(Reporter: jonsmirl, Assigned: netscape)
References
Details
It would aid in debugging and install problems if all binaries (exe, dll) for
the Windows platforms included a version resource to better identify the origin
of the file. These are easy to add, minor version numbers could be
automatically generated from CVS checkin version numbers.
To see an example pick a Microsoft dll from explorer, right click on it and
pick properties. There will be a tab that says version if the file contains a
version resource. The view dependencies program also shows the version resource.
Comment 1•25 years ago
|
||
CVS checkin numbers from which file? Or do you want it to contain the CVS
checkin numbers of all files linked in?
Forget the part about CVS checkin numbers, I wasn't thinking clearly instead
you want system build numbers. You could write M16, M15 or wathever into the
comment field. This is just a way to identify when people mix versions or
don't know what they have installed. For example I have XPCOM standalone in my
environment and it can get mixed up with files of the same name from the
browser distribution. Date and timestamps on files can also get messed up by
people copying them.
This is just a nice feature but not critical.
Comment 3•24 years ago
|
||
This would be a nice feature, but then again its not critical as the reporter
said. Maybe we should mark this future as well? Markng as New.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 4•24 years ago
|
||
Transferring to default XPCOM owner.
Assignee: rayw → warren
Status: ASSIGNED → NEW
Updated•24 years ago
|
QA Contact: leger → kandrot
Comment 5•24 years ago
|
||
This would be a nice.
Reassigning again (sorry warren)
Assignee: warren → kandrot
QA Contact: kandrot → scc
Comment 7•24 years ago
|
||
I assume that this bug is for the XPCOM library.
Target Milestone: --- → mozilla1.0
Updated•23 years ago
|
Keywords: mozilla1.0
Comment 8•23 years ago
|
||
similar to http://bugzilla.mozilla.org/show_bug.cgi?id=53727
over to cls. Chris can you own this bug for mozilla 1.0>
*** This bug has been marked as a duplicate of 53727 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 10•22 years ago
|
||
*** Bug 182422 has been marked as a duplicate of this bug. ***
Comment 11•22 years ago
|
||
Being similiar doesn't make a bug a duplicate. so versioning is not the same as
windows version resources. Its two different platforms. If they are similiar,
they should all block a versioning META bug 80613. See also bug 23560 which set
the groundwork that can be extended to the rest of Mozilla by adding module.ver
files throughout.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 12•22 years ago
|
||
chris, i thought that the offical build sets this?
Assignee: dougt → seawood
Status: REOPENED → NEW
Assignee | ||
Comment 13•22 years ago
|
||
I don't know who's smoking what but Aki fixed this problem on win32 a long time ago.
*** This bug has been marked as a duplicate of 23560 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 22 years ago
Keywords: mozilla1.0
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•