initial structure
parent
348a3fec1d
commit
70edd074af
@ -1,3 +1,4 @@
|
||||
# signedpkg
|
||||
|
||||
signed and encrypted packages
|
||||
Signed and encrypted packages for deployment
|
||||
|
||||
|
@ -0,0 +1,25 @@
|
||||
# sigendpkg file format
|
||||
|
||||
The signedpkg file format defines a deployment archive, which contains:
|
||||
|
||||
- distribution archive in a file named DIST.A
|
||||
- distribution key in a file named DIST.KEY
|
||||
- distribution signature in a file named DIST.SIG
|
||||
|
||||
To use a signedpkg the user needs:
|
||||
|
||||
- deployment key
|
||||
- provisioning key
|
||||
|
||||
## distribution archive
|
||||
|
||||
The distribution archive contains a file and folder structure of files being
|
||||
deployed. In the main directory there are be only folders. The folder names
|
||||
in the main directory mark symbolic installation locations, which are user
|
||||
dependent.
|
||||
|
||||
In the p≡p project there are two such installation locations:
|
||||
|
||||
- PER_USER_DIRECTORY
|
||||
- PER_SYSTEM_DIRECTORY
|
||||
|
@ -0,0 +1,3 @@
|
||||
#!/bin/env python3
|
||||
|
||||
|
Loading…
Reference in New Issue