Wednesday, 6 March 2013

[gccsdk] Name conversion catches

I created a new topic for the sake of clarity.

> In message <b1ea532753.Jo@hobbes.bass-software.com>
> John Tytgat <John.Tytgat@aaug.net> wrote:

>> In message <f67e522753.beeb@ron1954.woosh.co.nz>
>> Ron <beeb@woosh.co.nz> wrote:

>>I still have the problem of textfile,xyz (where xyz is a recogniseable
>> extension) causing tar to skip it.
>> While it doesn't make much sense to have a file like that on the
>> RISC OS filesystem (It should have been already converted by program foo)
>> I'm aiming to be able to copy 'all' files verbatim and this is one
>> that catches.

>If you want to make that bullet proof Unixify should somehow escape the
>"," in the RISC OS file name and you have to teach riscosify to do the
>unescaping.

Mmm, I'll keep it it mind. It only has to be done if the RISC OS file is
type fff plus having ,xyz
Types other than fff will actually work, but they go under the guise
of non-textfile,xyz,xyz which is a bit messy looking but they do return
with the type they left RISC OS with.
I did try the force FFF ext riscosify option, but didn't see any
change.

>
>BTW, are RISC OS files "/" and "//" properly tar'd and can they be
>untar'd on Unix ? :-)

I checked Linux and you cant create "." or ".." but you can
create "..."
I have experimented and found I have my own conversion for the
parsed top directory doing an 'up directory' when named "/" and on
the subdirectories/files (tar internally) unixlib is just skipping
everything below a "/" or "//"

Neither is satisfactory, and I'm thinking that given the punter who
creates a RISC OS "/" or "//" has no intention to do either an 'up
directory' or create a folder with no name, I would convert
"./." ".//." ".///" to something like "/?/" "/??/" "/???/"
A character that isn't allowed in RISC OS ensures that there is no
possibly of a conflict with another object in the same directory.
Even though "..." and more is allowed in Linux I dont think it would
be necessary or make any difference to let those cases through as
"..." rather than "???"

Thanks for the heads up.
Ron M.

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

No comments:

Post a Comment