Packaging the new OSLib release

[alan buckley]

Hi I'd like to update my OSLib package at the
RISC OS packaging site to the new 7.00 version.

To do so I think it would be simpler if I could
include all the different builds of the library
in a single !OSLib directory. Would you object
if I did this?

To be able to do this it needs that the only
difference between the various downloads is
the library files themselves (i.e. not the
headers or documentation). Is this the case?

Also I will need to give different names to
the various variants of OSLib for the different
builds. Is this OK with you? If so do you have
any preferred nameing convention. My initial
thoughts were a code so we got.

libOSLib32.a - standard soft-float unixlib build
libOSLib32h.a - hard-float unixlib build
libOSLib32s.a - SCL build
libOSLib32m.a - Module build

The old AOF build can remain the same as it is
put in an "o" directory.

(similar changes would be made to the support
library).

Regards,
Alan