Updating !Boot and !System
dave at davehigton.me.uk
Fri Feb 19 21:25:57 GMT 2016
In message <55547cd825webpages at sprow.co.uk>
Sprow <webpages at sprow.co.uk> wrote:
>In article <1016645455.DaveMeUK at my.inbox.com>,
> Dave Higton <dave at davehigton.me.uk> wrote:
>> In message <55545d0a67chris at chris-johnson.org.uk>
>> cj <chris at chris-johnson.org.uk> wrote:
>> >In article <8206585455.DaveMeUK at my.inbox.com>,
>> > Dave Higton <dave at davehigton.me.uk> wrote:
>> >> What is this "installer module"?
>> >*h. installer
>> >==> Help on keyword Installer
>> >Module is: Installer 0.13 (19 Jul 2012)
>> It still looks like a struggle to use it, though. According to
>> the help, it can only cope with a single file per command, and
>> it has to be given both the source path (which we know) and the
>> destination path.
>How many files are present in the !Boot/!System updates from NetSurf?
>CI 3419 has
> 13 in !Cache
> 5 in !System
> 78 in !Unicode
>so it's not beyond the wit of man to have 91 lines in an obey file, assuming
>you use some tool to get their leaf names (or, I suppose, a bit of perl or
>whatever to generate the script by the build system).
Today I've been writing a small BASIC prog to recurse through all
the files in a folder and use Install_Update to update the copy
in a similar location within Boot$Dir or System$Dir as appropriate.
It's not crunched and is only about 60 lines. It does rely on the
relative path in the real Boot$Dir/System$Dir being identical to
that in the !Boot/!System that we provide - that must be so,
mustn't it? Currently it doesn't attempt to add folders that don't
already exist in the destination, so it would fail if we added a
new folder. I think this must be a very rare event. It wouldn't
be difficult to support it if required.
It still doesn't compare the file contents, so, just like the
pure Copy process, it will typically update more often than needed.
I've written some multi-tasking comparison code elsewhere, and
I'll see if I can build it into the above tool.
>> And it still copies based on the file date (which we know we
>> can't trust) and not the file content.
>Not so. See section 5.2 of the spec
Thank you for that... more info that I didn't even know existed!
However... most of our files are not modules, and not exceptions
as described in the doc, so they're updated on the basis of file
date. The modules are based on version number, and when we put
out a new version, they will have a recent date... so it amounts
to the same thing. When we just put out the same version number
but a later file date, which is what happens rather a lot, they
/will/ be updated on the basis of file date. At least we won't
be bothered by the clashes that exist between the ROL and ROOL
Can't remember your password? Do you need a strong and secure password?
Use Password manager! It stores your passwords & protects your account.
Check it out at http://mysecurelogon.com/password-manager
More information about the netsurf-dev