mirror/flatpak
1
0
Fork 0
mirror of https://github.com/flatpak/flatpak.git synced 2026-05-18 21:55:22 -04:00
Code Issues Packages Projects Releases Wiki Activity

README: some Formatting tweaks

Browse Source 
Fix capitalization of Flatpak in a few places,
and make directory names appear as such.

Closes: #2545
Approved by: mwleeds
This commit is contained in:
Matthias Clasen
2019-01-08 13:04:49 -05:00
committed by Atomic Bot
parent d157d9ea18
commit 43440454af
1 changed files with 13 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@@ -81,17 +81,18 @@ integration will not work. However, if the system installation is
synchronized, you can often use the system installed helper instead—
at least if the two versions are close in versions.
Floor plan
==========
# This repository
The flatpak project consists of multiple pieces, and it can be
The Flatpak project consists of multiple pieces, and it can be
a bit challenging to find your way around at first. Here is a
quick intro to the major components of the repo:
* common: contains the library, libflatpak. It also contains various pieces of code that are shared between the library, the client and the services. Non-public code can be recognized by having a `-private.h` header file.
* app: the commandline client. Each command has a `flatpak-builtins-` source file
* data: D-Bus interface definition files
* session-helper: The flatpak-session-helper service, which provides various helpers for the sandbox setup at runtime
* system-helper: The flatpak-system-helper service, which runs as root on the system bus and allows non-root users to modify system installations
* portal: The Flatpak portal service, which lets sandboxed apps request the creation of new sandboxes
* doc: The sources for the documentation, both man pages and library documentation
* tests: The testsuite
quick intro to the major components of the flatpak repo:
* `common`: contains the library, libflatpak. It also contains various pieces of code that are shared between the library, the client and the services. Non-public code can be recognized by having a `-private.h` header file.
* `app`: the commandline client. Each command has a `flatpak-builtins-` source file
* `data`: D-Bus interface definition files
* `session-helper`: The flatpak-session-helper service, which provides various helpers for the sandbox setup at runtime
* `system-helper`: The flatpak-system-helper service, which runs as root on the system bus and allows non-root users to modify system installations
* `portal`: The Flatpak portal service, which lets sandboxed apps request the creation of new sandboxes
* `doc`: The sources for the documentation, both man pages and library documentation
* `tests`: The testsuite