Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
@@ -21,13 +21,13 @@ This is a draft - comments/discussion/edits are **WELCOME**
...
@@ -21,13 +21,13 @@ This is a draft - comments/discussion/edits are **WELCOME**
## Concepts
## Concepts
*`archive`: archive containing project source code (also known as tarball).
***archive**: archive containing project source code (also known as tarball).
*`distro`: operating system distribution such as Debian, Fedora, Arch, NixOS, etc.
***distro**: operating system distribution such as Debian, Fedora, Arch, NixOS, etc.
*`repo`: `git` (or other VCS) repository containing project sources
***repo**: `git` (or other VCS) repository containing project sources
*`package`: package archive accepted by a package manager of particular OS distribution
***package**: package archive accepted by a package manager of particular OS distribution
*`source package`: files needed in order to build a package (this varies a lot between distros, for example RPMs are built from a single `.src.rpm` source package while `.deb` packages are built from several files)
***source package**: files needed in order to build a package (this varies a lot between distros, for example RPMs are built from a single `.src.rpm` source package while `.deb` packages are built from several files)
*`packaging style`: processes associated with packaging for specific family of distros (for example `deb` packaging style is used on Debian, Ubuntu, and their clones)
***packaging style**: processes associated with packaging for specific family of distros (for example `deb` packaging style is used on Debian, Ubuntu, and their clones)
*`packaging template`: files needed to build a source package; this could be called "packaging sources" but I suggest using "template" instead in order to avoid confusion with `source package`.
***packaging template**: files needed to build a source package; this could be called "packaging sources" but I suggest using "template" instead in order to avoid confusion with `source package`.