AOSC Wiki / AOSC OS / AOSC/Retro / .
Also available in: 简体中文

AOSC OS/Retro: An Introduction to Users and Maintainers (RFC)

Enjoying AOSC OS on Your Retro Devices

Now that we have introduced our rationale to maintaining a Retro branch for AOSC OS (we will now refer to this as AOSC OS/Retro), this page will serve as an introduction to our design specifications and goals in maintaining this branch.

Specifications§

In terms of end-user experience and management characteristics, AOSC OS/Retro is a standard AOSC OS distribution. However, changes are made in terms of dependencies, features, and maintenance schedules. In brief, AOSC OS/Retro will...

Now, we will present the commonalities and differences in detail.

Target Architectures§

AOSC OS/Retro currently targets the following architectures...

Common Components and Tools§

As AOSC OS/Retro is not a fork but a branch of the mainline AOSC OS distribution, it will share not only the package tree, but also the Core and the maintenance tools as the mainline...

Dependencies§

As AOSC OS/Retro targets storage and performance constraint devices, unlike its mainline counterpart, AOSC OS/Retro will ship packages with minimal optional feature enabled. Listed below are a few general rules to be followed...

Distribution Features§

AOSC OS/Retro will ship in two flavours, "Base" and "Base/X11." Both flavours will come fully localised (once locale is enabled by the end-user) as well as a generic, non-optimised Linux Kernel for their respective

The Base/X11 variant will come with the following additional components (the list below is subject-to-change)...

Extra packages, such as Firefox and more feature-complete desktop environments will be available from the community repository, however, hardware requirement checks will be enforced based on processor and memory installed on your AOSC OS/Retro device (i.e., package installation will be aborted when attempting to install Firefox on a computer without SSE2 SIMD support).

Maintenance Schedules§

AOSC OS/Retro will be maintained on the retro branch, sharing the same package tree with the mainline distribution. However, in interest of both the maintainer's reasonable maintenance effort, as well as the longevity and usability of the target devices, AOSC OS/Retro will update on an annual schedule.

After the first update cycle of a year, the retro branch will merge from the stable branch from the mainline distribution (stable => retro). After which, no further merge or reverse merge will be allowed. Package versions in the retro branch will remain constant unless...

At the end of each annual cycle, a new distribution tarball will be made available on the downloads page, as well as an update CD image containing a local repository containing all system updates. A full AOSC OS/Retro repository will also be provided in forms of a tarball or a set of CD/DVD image.

Goals§

AOSC OS/Retro will be maintained with a few goals in mind, relating to system performance, storage requirements, and peripheral support. This chapter will also serve to outline AOSC OS/Retro's system requirements.

This chapter will then be split into sections, containing requirements and metrics shared and specific to each of our target architectures.

Common Metrics§

System Performance (x86)§

On the 32-bit x86 architecture, AOSC OS/Retro "Base" requires the following system components...

AOSC OS/Retro "Base/X11" requires the following system components...

System Performance (PowerPC 32-bit, Big Endian)§

AOSC OS/Retro "Base" or "Base/X11" should run on all supported devices on this architecture - that is, PowerPC-based Apple Macintosh computers with New World ROM support.