... | ... | @@ -27,14 +27,14 @@ This is a draft - comments/discussion/edits are **WELCOME** |
|
|
* **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)
|
|
|
* **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".
|
|
|
|
|
|
|
|
|
## Conventions
|
|
|
|
|
|
`apkg` is to be invoked in a local `git` copy of a project to be packaged if applicable.
|
|
|
`apkg` is to be invoked in a local copy of a project repo to be packaged if applicable.
|
|
|
|
|
|
`apkg` operates on a current `git` commit by default/unless specified otherwise. Behavior might differ between commits with and without version tag (such as `v1.0.0`) but operation and outputs must be consistent from user point of view and always carried out in context of respective upstream git commit.
|
|
|
`apkg` operates on a current repo commit by default/unless specified otherwise. Behavior might differ between commits with and without version tag (such as `v1.0.0`) but operation and outputs must be consistent from user point of view and always carried out in context of respective upstream git commit when applicable.
|
|
|
|
|
|
|
|
|
### Input
|
... | ... | |