AelinandPablo Correa Gómez
0e41c1bcbd
Add firmware packaging guidelines to the documentation. The goal behind this was to make it so that it is very clear which packaging method is preferred for which cases to avoid fragmentation and inconsistency in pmaports packaging. Co-authored-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org> Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8161>
29 lines
666 B
Markdown
29 lines
666 B
Markdown
# Welcome to pmaports' documentation!
|
|
|
|
pmaports is the repository that holds the package build definitions in
|
|
postmarketOS.
|
|
|
|
When porting a new device or doing maintainance work around the distribution,
|
|
you will usually be working inside of pmaports.
|
|
|
|
This documentation section covers the Dos and Don'ts of packaging software
|
|
in pmaports and the processes around device categorization.
|
|
|
|
```{eval-rst}
|
|
.. toctree::
|
|
:hidden:
|
|
|
|
approval-rules
|
|
device-categorization
|
|
deviceinfo-reference
|
|
ci-tags
|
|
firmware
|
|
generic-device-packages
|
|
generic-kernels
|
|
kconfig-fragments
|
|
kconfigcheck
|
|
kernel-cmdline
|
|
kernel-versions
|
|
packaging-guidelines
|
|
```
|