In message <bb6367d953....@abbeypress.net> Jim Nagel <nets...@abbeypress.co.uk> wrote:
> Brian Jordan wrote on 13 Feb: > >> In article <9b5f51d953....@abbeypress.net>, >> Jim Nagel <nets...@abbeypress.co.uk> wrote: >>> Suggestion to the Netsurf team: > >>> Please, could you include an extra "Readme-date" file in the download >>> zipfile that would simply state in plain text the date of the last >>> actual change and words to the effect that "If you have updated !Boot >>> and !System since this date, there is no need to do it this time." > >>> It would save the chore of going to every machine and repepetititively >>> performing the merge-boot and merge-system rigamarole when it isn't >>> necessary. (The rest of the job of updating the !Netsurf application >>> on all stations can be done over the network.) Thanks. > > >> I work on the assumption that if a merge-boot or merge-system is required >> that NetSurf will let me know with an appropriate message. Otherwise I >> just let NetSurf get on with it. Am I under vigilant or are you over >> vigilant? It seems to me that the NetSurf team have far bigger fish than >> this to fry. > > Maybe I am being overpunctilious, but I'm just following the > instructions in the existing&unchanging Readme that comes as part of > the download. > >>From what you say, I can see that Netsurf might give a warning about a > module being out of date. But the Unicode stuff is not modules: > would Netsurf warn if any Unicode files are missing or outdated? > > I am in the 'ALWAYS update !Boot and !System' camp. I often notice, when doing so, that the hourglass/percentage twitches briefly into life, which suggests that something is being overwritten, i.e., altered, presumably necessarily. -- george greenfield