Abuild and Helpers: Difference between revisions
mNo edit summary |
m (Description of the abuild tree moved to Abuild tree) |
(No difference)
|
Revision as of 03:43, 8 December 2011
The abuild script and its friends are installed automatically along with the alpine-sdk package. The git repository contains always the lastest version of the scripts, example-files, and makefiles.
Fetch latest abuild
While inside your build environment you need to have the set of scripts/makefiles/etc.
apk add alpine-sdk cd ~ git clone git://dev.alpinelinux.org/abuild
When the above is done you might be interested in fetching the latest updates.
cd ~ git pull
Package build helpers
abuild-keygen
For abuild a public/private rsa key pair is needed. The abuild-keygen
command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode
abuild-sign
abuild-sign is for signing indexes.
abuild-sign [-hq] [-k PRIVKEY] [-p PUBKEY] INDEXFILE...
abuild-sign options
- -h Show this help
- -k The private key to use for signing
- -p The name of public key. apk add will look for /etc/apk/keys/PUBKEY
abuild-tar
abuild-tar [--hash[=<algorithm>]] [--cut]
abuild-tar options
- --hash[=sha1|md5] Read tar archive from stdin, precalculate hash for regular entries and output tar archive on stdout
- --cut Remove the end of file tar record
abump
The abuild script and its friends are installed automatically along with the alpine-sdk package. The git repository contains always the lastest version of the scripts, example-files, and makefiles.
Fetch latest abuild
While inside your build environment you need to have the set of scripts/makefiles/etc.
apk add alpine-sdk cd ~ git clone git://dev.alpinelinux.org/abuild
When the above is done you might be interested in fetching the latest updates.
cd ~ git pull
Package build helpers
abuild-keygen
For abuild a public/private rsa key pair is needed. The abuild-keygen
command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode
abuild-sign
abuild-sign is for signing indexes.
abuild-sign [-hq] [-k PRIVKEY] [-p PUBKEY] INDEXFILE...
abuild-sign options
- -h Show this help
- -k The private key to use for signing
- -p The name of public key. apk add will look for /etc/apk/keys/PUBKEY
abuild-tar
abuild-tar [--hash[=<algorithm>]] [--cut]
abuild-tar options
- --hash[=sha1|md5] Read tar archive from stdin, precalculate hash for regular entries and output tar archive on stdout
- --cut Remove the end of file tar record
abump
Template loop detected: Abump
apkgrel
abuild
Template loop detected: Abuild
APKBUILD generation
newapkbuild
To create the actual APKBUILD file newapkbuild can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided.
Template loop detected: Newapkbuild
apkbuild-cpan
apkbuild-pypi
Template loop detected: Apkbuild-pypi
Misc tools
buildlab
More details can be found at the buildlab page.
buildrepo
Template loop detected: Buildrepo
apkgrel
abuild
The abuild script and its friends are installed automatically along with the alpine-sdk package. The git repository contains always the lastest version of the scripts, example-files, and makefiles.
Fetch latest abuild
While inside your build environment you need to have the set of scripts/makefiles/etc.
apk add alpine-sdk cd ~ git clone git://dev.alpinelinux.org/abuild
When the above is done you might be interested in fetching the latest updates.
cd ~ git pull
Package build helpers
abuild-keygen
For abuild a public/private rsa key pair is needed. The abuild-keygen
command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode
abuild-sign
abuild-sign is for signing indexes.
abuild-sign [-hq] [-k PRIVKEY] [-p PUBKEY] INDEXFILE...
abuild-sign options
- -h Show this help
- -k The private key to use for signing
- -p The name of public key. apk add will look for /etc/apk/keys/PUBKEY
abuild-tar
abuild-tar [--hash[=<algorithm>]] [--cut]
abuild-tar options
- --hash[=sha1|md5] Read tar archive from stdin, precalculate hash for regular entries and output tar archive on stdout
- --cut Remove the end of file tar record
abump
Template loop detected: Abump
apkgrel
abuild
Template loop detected: Abuild
APKBUILD generation
newapkbuild
To create the actual APKBUILD file newapkbuild can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided.
Template loop detected: Newapkbuild
apkbuild-cpan
apkbuild-pypi
Template loop detected: Apkbuild-pypi
Misc tools
buildlab
More details can be found at the buildlab page.
buildrepo
Template loop detected: Buildrepo
APKBUILD generation
newapkbuild
To create the actual APKBUILD file newapkbuild can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided.
The abuild script and its friends are installed automatically along with the alpine-sdk package. The git repository contains always the lastest version of the scripts, example-files, and makefiles.
Fetch latest abuild
While inside your build environment you need to have the set of scripts/makefiles/etc.
apk add alpine-sdk cd ~ git clone git://dev.alpinelinux.org/abuild
When the above is done you might be interested in fetching the latest updates.
cd ~ git pull
Package build helpers
abuild-keygen
For abuild a public/private rsa key pair is needed. The abuild-keygen
command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode
abuild-sign
abuild-sign is for signing indexes.
abuild-sign [-hq] [-k PRIVKEY] [-p PUBKEY] INDEXFILE...
abuild-sign options
- -h Show this help
- -k The private key to use for signing
- -p The name of public key. apk add will look for /etc/apk/keys/PUBKEY
abuild-tar
abuild-tar [--hash[=<algorithm>]] [--cut]
abuild-tar options
- --hash[=sha1|md5] Read tar archive from stdin, precalculate hash for regular entries and output tar archive on stdout
- --cut Remove the end of file tar record
abump
Template loop detected: Abump
apkgrel
abuild
Template loop detected: Abuild
APKBUILD generation
newapkbuild
To create the actual APKBUILD file newapkbuild can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided.
Template loop detected: Newapkbuild
apkbuild-cpan
apkbuild-pypi
Template loop detected: Apkbuild-pypi
Misc tools
buildlab
More details can be found at the buildlab page.
buildrepo
Template loop detected: Buildrepo
apkbuild-cpan
apkbuild-pypi
The abuild script and its friends are installed automatically along with the alpine-sdk package. The git repository contains always the lastest version of the scripts, example-files, and makefiles.
Fetch latest abuild
While inside your build environment you need to have the set of scripts/makefiles/etc.
apk add alpine-sdk cd ~ git clone git://dev.alpinelinux.org/abuild
When the above is done you might be interested in fetching the latest updates.
cd ~ git pull
Package build helpers
abuild-keygen
For abuild a public/private rsa key pair is needed. The abuild-keygen
command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode
abuild-sign
abuild-sign is for signing indexes.
abuild-sign [-hq] [-k PRIVKEY] [-p PUBKEY] INDEXFILE...
abuild-sign options
- -h Show this help
- -k The private key to use for signing
- -p The name of public key. apk add will look for /etc/apk/keys/PUBKEY
abuild-tar
abuild-tar [--hash[=<algorithm>]] [--cut]
abuild-tar options
- --hash[=sha1|md5] Read tar archive from stdin, precalculate hash for regular entries and output tar archive on stdout
- --cut Remove the end of file tar record
abump
Template loop detected: Abump
apkgrel
abuild
Template loop detected: Abuild
APKBUILD generation
newapkbuild
To create the actual APKBUILD file newapkbuild can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided.
Template loop detected: Newapkbuild
apkbuild-cpan
apkbuild-pypi
Template loop detected: Apkbuild-pypi
Misc tools
buildlab
More details can be found at the buildlab page.
buildrepo
Template loop detected: Buildrepo
Misc tools
buildlab
More details can be found at the buildlab page.
buildrepo
The abuild script and its friends are installed automatically along with the alpine-sdk package. The git repository contains always the lastest version of the scripts, example-files, and makefiles.
Fetch latest abuild
While inside your build environment you need to have the set of scripts/makefiles/etc.
apk add alpine-sdk cd ~ git clone git://dev.alpinelinux.org/abuild
When the above is done you might be interested in fetching the latest updates.
cd ~ git pull
Package build helpers
abuild-keygen
For abuild a public/private rsa key pair is needed. The abuild-keygen
command from abuild package generates and configures the security keys.
$ doas abuild-keygen -a -i
abuild-keygen options
- -a Set PACKAGER_PRIVKEY=<generated key> in abuild.conf
- -i Install public key into /etc/apk/keys using sudo
- -h Show this help
- -n Non-interactive. Use defaults
- -q Quiet mode
abuild-sign
abuild-sign is for signing indexes.
abuild-sign [-hq] [-k PRIVKEY] [-p PUBKEY] INDEXFILE...
abuild-sign options
- -h Show this help
- -k The private key to use for signing
- -p The name of public key. apk add will look for /etc/apk/keys/PUBKEY
abuild-tar
abuild-tar [--hash[=<algorithm>]] [--cut]
abuild-tar options
- --hash[=sha1|md5] Read tar archive from stdin, precalculate hash for regular entries and output tar archive on stdout
- --cut Remove the end of file tar record
abump
Template loop detected: Abump
apkgrel
abuild
Template loop detected: Abuild
APKBUILD generation
newapkbuild
To create the actual APKBUILD file newapkbuild can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided.
Template loop detected: Newapkbuild
apkbuild-cpan
apkbuild-pypi
Template loop detected: Apkbuild-pypi
Misc tools
buildlab
More details can be found at the buildlab page.
buildrepo
Template loop detected: Buildrepo