Skip to content

AOSC-Dev/aosc-os-abbs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

AOSC OS ABBS Tree

The AOSC OS ABBS Tree contains build configurations and scripts for all packages made available in the official AOSC OS repository, organised in a tree-like fashion. The "Tree" is split into three main classes and various sub-categories:

  • core-* contains components of the AOSC OS Core.
  • app-* contains applications.
  • desktop-* contains desktop environments and their supporting libraries.
  • lang-* contains programming language support stacks.
  • meta-* contains meta packages (*-base).
  • runtime-* contains runtime libraries and data.

Branches

The ABBS Tree is maintained in a multi-branch fashion, for more information, please refer to the AOSC OS Maintenance Guidelines.

Groups

When using ACBS (Autobuild CI Build System), it is possible to build a series of packages with a single command. This is achieved by the "groups" defined in the groups/ directory, with files defining a list of packages to build.

Notes for developers on Windows

Currently, this repository cannot be checked out on Windows, since there are backslashes (\) in file names, specifically required by systemd.mount for string escaping, which is not a valid Windows file name. Notebly, repository checkout will also fail in MinGW or Cygwin environments for the same reason. We recommend using Windows Subsystem for Linux (WSL) to work on this repository. In case you missed it, AOSC OS on WSL is available on Microsoft Store!

Further Readings

Useful Links

Need Help?

Please report any build-time and run-time issues using our issues page.