Commit 16159adc authored by Bernhard Landauer's avatar Bernhard Landauer

update README

parent d6d55477
......@@ -69,16 +69,17 @@ You can also build `any` packages, which will use the aarch64 architecture to bu
sudo buildarmpkg -p package -a any
```
This places the packages created inside `/var/cache/manjaro-arm-tools/pkg/` in the architecture folder.
The built packages will be copied to `$PKGDIR` as specified in `/usr/share/manjaro-arm-tools/lib/manjaro-arm-tools.conf` and placed in a subdirectory for the respective architecture.
Default package destination is `/var/cache/manjaro-arm-tools/pkg/`.
## deployarmpkg
This script is only for package maintainers of Manjaro-ARM.
This script assumes that you have enabled GPG signing on your machine, that you have a working key-pair and that you have a user on the Manjaro-ARM main server.
The `-p` option needs to be only the package. Not the full path to the package.
It will gpg sign and uploud the package you mention to the Manjaro-ARM main server.
It will gpg sign and upload the package(s) you mention to the Manjaro-ARM main server.
This script assumes that you have enabled GPG signing on your machine, that you have a working key-pair and that you have a user on the Manjaro-ARM main server.
For the `-p` option use just `$pkgname` without path or extension.
Multiple packages can be specified by repeating `-p` option.
**Syntax**
......@@ -89,16 +90,16 @@ deployarmpkg -p package [-a architecture] -r repo -k keyid
To upload a package to the aarch64 extra repo use:
```
deployarmpkg -p package.pkg.tar.xz -a aarch64 -r extra -k email@server.org
deployarmpkg -p package -a aarch64 -r extra -k email@server.org
```
To upload an any package to the community repo use:
```
deployarmpkg -p package.pkg.tar.xz -a any -r community -k email@server.org
deployarmpkg -p package -a any -r community -k email@server.org
```
This should be used after creating a package with `buildarmpkg` and cd'ing to the cache folder. It will sign the package with your default secret GPG key and upload both files
This should be used after creating a packages with `buildarmpkg`. It will sign the package(s) with your default secret GPG key, upload the package and signature files
and remove the local files.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment