Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#193 closed defect (fixed)

update_seg emits strange ordering of entries in Installations.info

Reported by: Eric Swenson Owned by: Gary Dixon
Priority: major Milestone: MR12.7
Component: Tools Version: MR12.6f
Keywords: Cc:

Description

I would expect update_seg to prepend entries to Installations.info, or perhaps sort them in reverse chronological order. I installed MCR10067 today and got this at the front of my Installations.info:

10/20/19:
MCR10066: Change multiple-entry info seg to treat .errata.info names as General
Information segs (MR12.6g-0031).

10/20/19:
MCR10067: Fix bug190 which causes hcom to display history comment errors in the -orig PATH as if they appeared in the source PATH
\c(MR12.6g-0032).

09/20/19:
MCR10065: Add support for history_comment entries in info segments.
(MR12.6g-0030)

08/17/18:
MCR10051: Updated (status date) in lisp to return 4-digit year.
Updated lisp interpreter, lisp compiler, and emacs.
(MR12.6g-0014)

...

Change History (5)

comment:1 by Gary Dixon, 7 years ago

Owner: changed from Eric Swenson to Gary Dixon
Status: newassigned

comment:2 by Gary Dixon, 7 years ago

A workaround for this problem is to manually add the following header to start of your Installations.info file:

Reverse chronological list of system software changes.


This line must appear exactly at top of Installations.info file, and must be followed by one blank line.

Each new entry will be added after this header, and before already existing entries. When the above header does not begin the file, then each new entry is added after the first blank line (NLNL sequence) in the file. Each new entry with two blank lines (the help paragraph separator).

comment:3 by Gary Dixon, 7 years ago

Status: assignedaccepted

comment:4 by Gary Dixon, 7 years ago

Component: DocumentationTools
Milestone: MR12.6g
Resolution: fixed
Status: acceptedclosed

Fixed by MCR10068

comment:5 by Eric Swenson, 7 years ago

Milestone: MR12.6gMR12.7

Milestone renamed

Note: See TracTickets for help on using tickets.