ladybird/Documentation/FAQ.md

# Frequently Asked Questions about SerenityOS

## Will SerenityOS support `$THING`?

Maybe. Maybe not. There is no plan.

## When will you implement `$THING`?

Maybe someday. Maybe never. If you want to see something happen, you can do it yourself!

## Where are the ISO images?

There are no ISO images. This project does not cater to non-technical users.

## Well, how do I run this thing then?

Simple, my friend! Just refer to the [build instructions](BuildInstructions.md).

## Why is the system 32-bit?

The system was originally 32-bit only, since that's what Andreas was most familiar with when starting out. Nowadays, there is a 64-bit port as well (Intel/AMD x86\_64)

## I did a `git pull` and now the build is broken! What do I do?

If it builds on CI, it should build for you too. You may need to rebuild the toolchain. If that doesn't help, try it with a clean repo.

If you can't figure out what to do, ask in the `#build-problems` channel on Discord.

## Why don't you use `$LIBRARY` instead of implementing `$FEATURE` yourself?

The SerenityOS project tries to maximize hackability, accountability, and fun(!) by implementing everything ourselves.

## Does SerenityOS have a package manager?

No, SerenityOS does not have a package manager. The project uses a monorepo approach, meaning that all software is built in the same style and using the same tools. There is no reason to have something like a package manager because of this.

*However* there are ports which can be found in the [Ports directory](../Ports). A port is a piece of software that can optionally be installed, might not have been built by us, but supports running on SerenityOS. They act quite similarly to packages, each coming with their own install script.

Currently when running the system in a virtual machine, ports need to be cross compiled on the host, and added to the file system image before booting. Then it's also possible to configure the build system to [in- or exclude components](./AdvancedBuildInstructions.md#component-configuration) from a build.
Documentation: Update FAQ a bit and move it into Documentation/ This was hiding on the serenityos.org website previously, where not many people found it. Let's put it in a more natural location, and also make sure to link to it from the README. 2021-05-05 18:03:02 +00:00			`# Frequently Asked Questions about SerenityOS`

			## Will SerenityOS support `$THING`?

			`Maybe. Maybe not. There is no plan.`

			## When will you implement `$THING`?

			`Maybe someday. Maybe never. If you want to see something happen, you can do it yourself!`

			`## Where are the ISO images?`

			`There are no ISO images. This project does not cater to non-technical users.`

Documentation: Add FAQ entry about running the system 2022-02-02 20:36:40 +00:00			`## Well, how do I run this thing then?`

			`Simple, my friend! Just refer to the [build instructions](BuildInstructions.md).`

Documentation: Update FAQ a bit and move it into Documentation/ This was hiding on the serenityos.org website previously, where not many people found it. Let's put it in a more natural location, and also make sure to link to it from the README. 2021-05-05 18:03:02 +00:00			`## Why is the system 32-bit?`

Documentation: Amend FAQ about the system being 32-bit only People still ask about this all the time, so let's keep the question but amend it with the fact that we now have 64-bit support as well. 2021-08-15 11:02:48 +00:00			`The system was originally 32-bit only, since that's what Andreas was most familiar with when starting out. Nowadays, there is a 64-bit port as well (Intel/AMD x86\_64)`
Documentation: Update FAQ a bit and move it into Documentation/ This was hiding on the serenityos.org website previously, where not many people found it. Let's put it in a more natural location, and also make sure to link to it from the README. 2021-05-05 18:03:02 +00:00
			## I did a `git pull` and now the build is broken! What do I do?

			`If it builds on CI, it should build for you too. You may need to rebuild the toolchain. If that doesn't help, try it with a clean repo.`

			If you can't figure out what to do, ask in the `#build-problems` channel on Discord.

			## Why don't you use `$LIBRARY` instead of implementing `$FEATURE` yourself?

Documentation: Add a package manager section to the FAQ People are commonly asking about a package manager in serenity. This patch adds an answer the FAQ, explaining why there is no need for packages as well as different possible ways to add or remove software installed on the system. 2021-07-09 18:12:55 +00:00			`The SerenityOS project tries to maximize hackability, accountability, and fun(!) by implementing everything ourselves.`

			`## Does SerenityOS have a package manager?`

			`No, SerenityOS does not have a package manager. The project uses a monorepo approach, meaning that all software is built in the same style and using the same tools. There is no reason to have something like a package manager because of this.`

Docs: FAQ: Improve grammar in 2 paragraphs 2022-07-04 21:29:57 +00:00			`However there are ports which can be found in the [Ports directory](../Ports). A port is a piece of software that can optionally be installed, might not have been built by us, but supports running on SerenityOS. They act quite similarly to packages, each coming with their own install script.`
Documentation: Add a package manager section to the FAQ People are commonly asking about a package manager in serenity. This patch adds an answer the FAQ, explaining why there is no need for packages as well as different possible ways to add or remove software installed on the system. 2021-07-09 18:12:55 +00:00
Docs: FAQ: Improve grammar in 2 paragraphs 2022-07-04 21:29:57 +00:00			`Currently when running the system in a virtual machine, ports need to be cross compiled on the host, and added to the file system image before booting. Then it's also possible to configure the build system to [in- or exclude components](./AdvancedBuildInstructions.md#component-configuration) from a build.`