Fyra Wiki - User contributions [en]

Ultramarine Linux

2023-10-01T12:59:20Z

KorewaChino: /* Notes */

[[Category:Fyra Labs]]
'''Ultramarine Linux''' is a [[wikipedia:Fedora|Fedora]]-based [[wikipedia:Linux|Linux]] distribution designed to be easy to use for everyone, from beginners to tech enthusiasts.
It provides sane-defaults such that "it just works" and minimal configurations are required before users can start using the system.

It comes with 4 editions, namely the Flagship Edition, the GNOME Edition, the Pantheon Edition, and the KDE Plasma Edition.
It also comes with several tweaks preapplied to make initial setup and daily usage seamless.

The Ultramarine Linux distribution is created and maintained by the '''Ultramarine Project''', which is led by '''Cappy Ishihara''' started in 2021, and later acquired by [[Fyra Labs]].

== Editions ==
=== CuteFish ===
Before the release of Ultramarine 37, the [[CuteFish]] Edition was provided but later deprecated due to CuteFish DE's lack of
development and (consequently) its buggy behaviour and broken dependencies. It was then removed and replaced by the KDE Plasma Edition.

=== Flagship ===
The Flagship Edition provides an elegant and simple interface with [[wikipedia:Budgie (desktop environment)|Budgie DE]].
The Budgie version used was packaged in the Ultramarine repository until Ultramarine 37, but it will switch to the one in the Fedora official repositories by Ultramarine 38.

=== GNOME ===
The GNOME Edition provides an intuitive layout with [[wikipedia:GNOME|GNOME]].

=== KDE Plasma ===
The KDE Plasma Edition is provided since the release of Ultramarine 37 and it comes with Latte dock. Its layout is heavily inspired by [[wikipedia:Pop!_OS|Pop!_OS]].
However, Latte dock was removed in Ultramarine 38 due to negative feedback and its buggy behaviour and replaced by the default KDE Plasma theme.

=== Pantheon ===
The Pantheon Edition provides the default desktop of [[wikipedia:Elementary OS|Elementary OS]], Pantheon DE.
The version in [[Terra]] was used since Ultramarine 37 as it was removed from the Fedora 37 repositories.


== Philosophy ==
Ultramarine Project, the team behind the development of Ultramarine Linux and its side projects, has the goal of making Ultramarine Linux an operating system that "just works", meaning customizations and tweaks don't have to be applied manually and things should work out of the box.

In addition to user experience, the infrastructure of the Project is also designed to be developer-friendly. One notable example is [[Terra]], which allows much easier creation and maintenance of RPM packages with the help of automatic updates when compared with Fedora.

== Features ==
Ultramarine Linux comes with a few repositories preinstalled, including [[wikipedia:RPM Fusion|RPM Fusion]], [[wikipedia:Flathub|Flathub]] and [[Terra]].
It also has its own repository with its sources [https://github.com/Ultramarine-Linux/ultramarine-pkgs/ hosted on GitHub] and powered by [[Andaman]].
The packages were hosted separately with their own git repository on a self-hosted GitLab instance and later GitHub, packaged using [[umpkg]].

It uses the [[wikipedia:Anaconda (installer)|Anaconda installer]], but it is said that there will be a custom installer.<ref group="note">The TUI installer <code>libcappy</code> is working but unused. Now deprecated in favor of Katsu and Readymade, a rewritten version in Rust.</ref> A welcome program for a better out-of-the-box experience is also planned and it is a work in progress.[https://github.com/Ultramarine-Linux/tauri-welcome]

== History ==
=== The Acquisition of the Ultramarine Project ===
[[Fyra Labs]] acquired the Ultramarine Project on 12 October, 2022 as agreed by both sides which
brought numerous advantages to the development of Ultramarine since both sides had been lacking manpower. After the acquisition, the team started work on numerous projects
which greatly changed the infrastructure and shaped the development of Ultramarine 37, making it arguably the biggest release.

=== The development of umpkg and Andaman ===
: Main Article: [[Andaman]]
Ultramarine had been using Koji for its own repository just like Fedora itself, but it made package maintenance difficult to do with its sheer complexity, which
led to the creation of [[umpkg]] by the Ultramarine Project. It reduces burden on packaging software and uploading them to the Koji server. However,
the sophisticated part (Koji itself) was still there, so a packaging tool was proposed. After the acquisition, the team started to work on
[[Andaman]] (aka. <code>anda</code>), which was originally intended to be a package manager, but later rewritten as a package build toolchain.

== Notes ==
<references group="note" />

Cappy Ishihara

2023-10-01T12:57:07Z

KorewaChino:

'''Pornpipat Popum''', better known as '''Cappy Ishihara''' is a Thai software and DevOps engineer who specializes in writing scripts for batch processing, automation and unattended workloads. They are the Chief Information Officer of [[Fyra Labs]]; and also the project lead for the [[Ultramarine Linux]], [[Terra]], and [[Andaman]] projects. Cappy is the co-founder of the Ultramarine Linux project, and its lead developer.

=== Career ===

==== Ultramarine Linux ====
Cappy co-founded the Ultramarine Linux project back in late 2021 alongside [[Paskal Sitepu]], an Indonesian Linux kernel hacker.

Ultramarine Linux was initially created as a testing platform for the ''Cutefish Desktop'', formerly known as ''Cyber Desktop'' back then.

Cappy Ishihara

2023-10-01T12:46:04Z

KorewaChino: Created page with "'''Pornpipat Popum''', better known as '''Cappy Ishihara''' is the Chief Information Officer, and also the product lead for the Ultramarine Linux, Terra, and Andaman projects. They are a software and DevOps engineer who specializes in writing scripts for batch processing, automation and unattended workloads."

'''Pornpipat Popum''', better known as '''Cappy Ishihara''' is the Chief Information Officer, and also the product lead for the [[Ultramarine Linux]], [[Terra]], and [[Andaman]] projects.

They are a software and DevOps engineer who specializes in writing scripts for batch processing, automation and unattended workloads.

Andaman

2023-06-10T09:35:31Z

KorewaChino: /* Configuration */ hcl note

[[Category:Fyra Labs]]
[[Category:Projects]]
'''Andaman''', often abbreviated as '''anda''', is a modern package build toolchain designed to
simplify building different package formats for different projects in the same repository.
It mainly supports monorepo setups, especially ones with CI support like GitHub. It currently supports building RPMs, OCI images and Flatpak packages.
It is written by [[Fyra Labs]] with the Rust programming language.

Anda's simplicity makes the packaging process seamless and it is most notably used in [[Terra]].

== Mechanisms ==
Currently, Anda is simply a meta-build system that calls upon other build systems to build and distribute packages. It reads the project manifest in <code>anda.hcl</code>
and calls the corresponding build system to build the package. Multiple projects can be included in a single repository (known as a ''monorepo'') recursively in different directories. The root directory contains a main configuration file (also <code>anda.hcl</code>) and the configurations will be inherited. All the other <code>anda.hcl</code> files in its subdirectory can independently represent multiple ''projects'', and multiple ways to build a package can be specified in each project. Once properly configured, a project can be built by <code>anda build ''subdirectory_path''/''project_name''</code>.

=== AndaX ===
'''AndaX''' is an embedded scripting system powered by [https://rhai.rs Rhai]. It is mainly for supporting automatic updates, but it is also the scripting system used behind
<code>pre_script</code> and <code>post_script</code>.

=== Automatic Updates ===
: See also: [https://developer.fyralabs.com/terra/autoupdate Fyra Developer: Terra autoupdate] for the supported functions in AndaX
Anda has refined support over automatically updating packages via the <code>anda update</code> command. The command finds all the projects with the file <code>update.rhai</code> in the same directory or if the configuration file has the <code>update</code> property set to a value:
<syntaxhighlight lang="js">
project project_name {
update = "path/to/update_script.rhai"
labels {
a = "1"
}
}
</syntaxhighlight>
Then, AndaX executes the script. Projects can also be filtered by adding <code>--filters key=value,key2=value2</code> to the command.
For example, the update script for the above project will be executed for <code>--filters a=1</code> or even without filters related to <code>a</code>, but
it won't be executed for <code>--filters a=2</code>.

== Configuration ==
Andaman uses the HashiCorp Configuration Language (HCL) for its configuration format, known for being used in software by HashiCorp such as Terraform, Consul, Vault and Packer. Its syntax is similar to UCL and NGINX's configuration format.

Consider the following. for <code>{ }</code> and <code>""</code>, they represent, respectively, an dictionary (empty by default) with keys and string values, and a string with no default value. Unless otherwise stated, all the attributes are optional.
<syntaxhighlight lang="js">
config {
mock_config = "" // default mock config for `anda build -c custom_mock_config`
strip_prefix = "" // strip prefix to form new project alias
strip_suffix = "" // strip suffix to form new project alias
project_regex = ""
}
project "project_name" { // the string quote is optional
rpm {
spec = "path/to/file.spec" // REQUIRED
sources = "."
package = ""
pre_script = "rpm_pre.rhai"
post_script = "rpm_post.rhai"
mock_config = ""
enable_scm = false
scm_opts { }
config { }
plugin_opts { }
macros { }
opts { }
}
podman tagname {
dockerfile = ""
import = ""
tag_latest = false
context = "" // REQUIRED
version = ""
}
docker tagname {
dockerfile = ""
import = ""
tag_latest = false
context = "" // REQUIRED
version = ""
}
flatpak {
manifest = "path/to/manifest.yml" // REQUIRED
pre_script = ""
post_script = ""
}
pre_script = "pre.rhai"
post_script = "post.rhai"
env { }
alias = [] // array of strings
scripts = [] // array of paths to AndaX scripts
labels { }
update = "update.rhai"
arches = ["x86_64", "aarch64"]
}
</syntaxhighlight>

== History ==
=== umpkg ===
In the very beginning, the [[Ultramarine]] Project had been using Koji for building RPM packages. Koji is the packaging system used by the [[wikipedia:Fedora Project|Fedora Project]]. However, Koji's sophistication makes it difficult to create and maintain RPM packages — it was said that the only person in the Ultramarine team who actually knew how to use Koji was the lead developer, [[Cappy Ishihara]]. Cappy was annoyed by the sheer complexity of building and uploading packages to Koji and made [[umpkg]], a packaging toolchain that runs on Mock and Koji. The creation of umpkg made it easier to create and maintain packages. However, umpkg still tightly integrates with Koji and uses the Koji API to trigger builds. Thus, an entirely new CI server was proposed.

=== RPM Frontend ===
The Ultramarine Project started work on Andaman on 9 Jun, 2022.
The name Andaman refers to the [[wikipedia:Andaman Sea|Andaman Sea]] next to Thailand, and follows the naming patterns for other projects related to Ultramarine.
Initially, Anda was written as a custom RPM frontend as an alternative to DNF that is similar to that of an AUR helper. However, there were issues with rust and RPM support.

=== CI Server ===
Anda was then rewritten as a CI Server that handles builds via BuildKit, stores artifacts and build infos, and later included a frontend to the server.
However, it slowly turned into a massive feature creep of projects.

=== Final rewrite ===
Thus, Anda was rewritten again and it finally became a build system for various package formats.