On Thu, Oct 11, 2012, at 02:04:08PM +0100, Graham Pickles wrote: >> The above (textfile) seems to be a very straight forward and pragmatic >> request, easy to implement and would be of assistance to many of us
An alternative approach (I have no idea of relative ease of implementation) would be to manually put real datestamps on the various modules etc once and for all, and on the outer shell of the !Boot and !System supplied, and then instruct the autobuilder not to willynilly change the datestamps. If necessary, could put the skeleton !Boot and !System in a zip within the download zip to protect their datestamps. The non-techie user then only has to glance at the date to determine whether it's necessary to merge !Boot and !System, or whether nothing has changed since the last merge a year-ish ago. Rob Kendrick wrote on Oct 11 at 14:18: > You know where to send patches :) I could make such a patch for !System, putting actual dates on the modules it contains and putting the latest of these dates on the shell. I'll do that and email it to you, Rob. However, as I said in an earlier post, we users out here have no way of knowing the actual revision date of the Unicode items, which is all that is contained within the !Boot skeleton. Every single file and directory is datestamped 2012-oct-02 14:18:01, presumably courtesy of the autobuilder in the twinkling of its eye. Perhaps you at Netsurf HQ have ways of determining the real dates. In practical terms, it would be enough just to stop the autobuilder from making further changes to this date for no reason. -- Jim Nagel www.archivemag.co.uk See you at London? www.riscoslondonshow.co.uk October 27
