On Wed 12 Jul, Nicholas Clark wrote:
> On Fri, Jul 07, 2000 at 10:40:19AM +0200, Vincent Lefevre wrote:
> > On Thu, Jul 06, 2000 at 13:28:19 +0100, Richard Proctor wrote:
> > But there could be name conflicts (this has already happen with an
> > old version of Perl, when the /pm wasn't needed). If your disc format
> > doesn't support long names, you can use raFS; this is what I do.
>
> There was certainly a conflict between .pm and .bs which sent dynaloaded
> modules into a spin.
>
> Personally it would seem safer if you're making the transition to a long
> name system to use a script to take each file and look for
> /package\s+[A-Za-z_0-9:]*([A-Za-z_0-9]+);/ and name the file "$1/pm"
>
> (with a backup copy of your tree in case things go wrong)
I resorted to writing a script to rename all the modules. I have used
a filetype for modules as well so that it is easy to transition between
This computer (now with RO4) and my other RPC which only has RO3.6.
I need to copy things both ways - depending on what I am doing.
I have used raFS as well in the past and I could use it on the other
machine, but I dont want to reconfigure it too much.
I have a backup on my old hard drive and as a complete copy on the new
drive. (Minor update of this machine from Arm700 to Kinetic SA, 400M to
20G HD, RiscOS from 3.5 to 4, Memory from 42M to 102M, Added a scanner,
1xCD to 48xCD...)
Richard
--
[EMAIL PROTECTED]