Correcting the behavior of sign in case of batch builds.
parent
22a87e131c
commit
d5c29f0879
|
|
@ -112,9 +112,9 @@ When releasing an AppImage, the developer can choose to sign the AppImage with
|
||||||
his own GPG signature.
|
his own GPG signature.
|
||||||
|
|
||||||
`loaih` can obviously sign your AppImage using your default GPG key, however
|
`loaih` can obviously sign your AppImage using your default GPG key, however
|
||||||
it **does not** do it by default with the `build` verb (we assume not everyone
|
it **does not** do it by default with both the `build` or the `batch` verbs:
|
||||||
would have the necessity to sign the AppImage, nor everyone possesses a valid
|
we assume not everyone would have the necessity to sign the AppImage, nor
|
||||||
GPG key). With the `batch` verb it does by default, instead.
|
everyone possesses a valid GPG key.
|
||||||
|
|
||||||
If you want to sign your AppImage with your default GPG key, be sure to add
|
If you want to sign your AppImage with your default GPG key, be sure to add
|
||||||
the option `--sign` (or in short `-s`).
|
the option `--sign` (or in short `-s`).
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue