[gccsdk] GCC 4.1.2 release 1 package won't upgrade from theprevious version
John.Tytgat at aaug.net
Thu Apr 26 14:24:45 PDT 2012
In message <SNT136-ds15802E26036002687CED09F0240 at phx.gbl>
"Alan Buckley" <alan_baa at hotmail.com> wrote:
> John Tytgat wrote on Wednesday, April 25, 2012:
> > Are you actually saying RiscPkg/PackMan isn't able to deal with filename
> > case changes between two versions of a package ?
> Yes I am saying that. The shared back-end (libpkg) to both versions uses
> an exact match to figure out which files it can overwrite during an upgrade
> so sees them as different files, but they won't be on the disc.
Naively I would have thought that an upgrade would be throwing away the
old !GCC application and installing the new !GCC copy. Why does it need
to take the file structure inside the application into account ?
> > If so, any chance to get
> > this fixed in RiscPkg/PackMan itself ?
> As it's difficult for you to change, I will email the author of libpkg to
> see if he can get it changed.
> Do you know if it is safe to assume that RISC OS filenames are not
> case sensitive?
I don't think you can assume that. It is at the discretion of the specific
FS. E.g. Sunfish isn't.
BTW, I know that FileSwitch happens to cache file info caseinsensitive,
at least for old versions of RISC OS, I don't know what the current
situation is. This is wrong IMHO. So if you write file 'FOO' and check
for the presence of 'foo' you might get a yes answer, even on caseinsensitve
FS. Probably a test like : create 'FOO', try to delete 'foo' and see if
that results in an error (if so, delete 'FOO').
> In the meantime people will need to uninstall GCC4 and then install it
> I was hoping you had the files on a disc somewhere still so you could
> just rename that one file and rebuild the one package.
If it would be just that, I would just have done this. ;-(
> Is this possible for the current release? If not, would it be OK with
> you if I rebuilt a new version of the package from your version with
> the one files case changed?
Sure feel free. Thanks for the offer.
> I will also pursue what can be done with libpkg to see the same
> problem doesn't occur in a future release.
John Tytgat, in his comfy chair at home BASS
John.Tytgat at aaug.net ARM powered, RISC OS driven
More information about the gcc