blob: 01a0c9e1c60a4750ebe2578a61b035333a5867a5 (
plain)
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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
pkgctl-release(1)
=================
Name
----
pkgctl-release - Release step to commit, tag and upload build artifacts
Synopsis
--------
pkgctl release [OPTIONS] [PATH...]
Description
-----------
Modified version controlled files will first be staged for commit,
afterwards a Git tag matching the pkgver will be created and finally
all build artifacts will be uploaded.
By default the target pacman repository will be auto-detected by querying
the repo it is currently released in. When initially adding a new package
to the repositories, the target repo must be specified manually.
Options
-------
*-m, --message* 'MSG'::
Use the given <msg> as the commit message
*-r, --repo* 'REPO'::
Specify target repository for new packages not in any official repo.
Using this option is disallowed if the package is already released, as it
would circumvent the auto-detection safeguard.
*-s, --staging*::
Build against the staging counterpart of the auto-detected repo
*-t, --testing*::
Build against the testing counterpart of the auto-detected repo
*-u, --db-update*::
Automatically update the pacman database after uploading
*-h, --help*::
Show a help text
See Also
--------
linkman:pkgctl-db-update[1]
include::include/footer.asciidoc[]
|