Software

Thirty years of RISC OS software, installed for you

The package manager puts software straight onto a machine's disc from the same repositories a real RISC OS machine uses. Applications, games, fonts and libraries, and it records what it installed so it can be taken off again cleanly.

Where it comes from

The repositories a real machine would use

RISC OS Open

The applications from the RISC OS disc image, built nightly, and a large third-party collection beside them.

The RISC OS Community

Where some newer work appears first. The released index is used rather than the testing one, which is unstable by design.

The preservation project

JASPP's catalogue of period commercial games, packaged to run on a machine like this one. Most need ADFFS, which is in the same index and comes along as a dependency.

Or your own

The source list is yours to edit. Add a repository, disable one, or point it somewhere else entirely.

How it behaves

Installing that can be undone

It records what it did

What each package put where is written to the machine's disc in the RISC OS Packaging Project's own format, so removal takes away what was added and other RISC OS package tools can see the same information.

Per machine

Software installed on one machine does not appear on another, because it went onto that machine's disc.

Checked on the way in

Downloads are verified against the index rather than trusted, so a truncated or altered file is refused instead of installed.

Findable

Section filters and a search box, because a list of hundreds of packages is only useful if you can get to the one you want.

Read more

The package manager needs a wxWidgets built with web request support, which some distributions do not provide, Debian 12 and the Raspberry Pi OS on it among them. Everything else still works there. ADFFS and the graphics card cannot both be used on one machine, and it warns you rather than letting you find out.