-
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrepo.texi
29 lines (24 loc) · 1.07 KB
/
repo.texi
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
@node Repo, , Pacscript, Top
@chapter Repo
This chapter is a reference for creating, maintaining, and using repositories.
@section Repository Structure
The structure of a repository should look something like this:
@example
package-repository/
├── packages/
│ ├── example-package1/
│ │ ├── example-package1.pacscript
│ │ └── .SRCINFO
│ └── example-package2/
│ ├── example-package2.pacscript
│ └── .SRCINFO
├── scripts/
│ ├── srcinfo.sh
│ ├── custom-script1.sh
│ └── custom-script2.sh
├── distrolist
├── packagelist
└── srclist
@end example
Some sort of GitHub Action like tool is recommended as well for package testing across swathes of distros and configurations.
Additionally, the use of pre-commit hooks are highly recommended, but not required. Generally, the @url{@value{GITHUBREPOURL}} team uses pre-commit hooks for formatting scripts, updating the @file{packagelist} file, and updating both the package @file{.SRCINFO} and the global @file{srclist}.