Package Manager Puzzle

I’m puzzled by this on two levels, so asking here on the ‘General’ forum to see what people suggest about where might be more appropriate for seeing something done…

Its about this, which seems to be being overlooked:

https://www.riscosopen.org/forum/forums/11/topics/13649

I may be misunderstanding, but I’d suspect this problem might put off a lot of people who try the SD card as their first experience of RO, hit the problem, and give up, possibly then being lost as a potential adopter or user. Yet the thread doesn’t seem to have prompted anyone setting about seeing if they can fix the problem. Is the above thread in the wrong place, so isn’t getting attention?

If someone comes up with a repro I’m sure it can be fixed.

At a guess its just a case of installing PackMan via PackMan in the SD image, so it can self-update. It’s part of a wider issue where the SD image includes lots of apps that haven’t come via PackMan so can’t be easily updated.

Alan Buckley coded an automated packager for me, I’m sure that could be used to auto build packages for apps that are in the SD image where there’s no maintained PackMan package available. Essentially everything that isn’t ROM based in $.Apps can be packaged and pre-deployed into the SD image so users can update any out of date packages as soon as they’ve installed the base SD image. It also allows for a smaller SD image as most apps aren’t used by the majority of people, so can be optionally installed after.

And on the subject of the SD image, why is there no separate ZIP of !Boot so we can keep it updated?