Difference between revisions of "Manjaro-tools"
Views
Actions
Namespaces
Variants
Tools
imported>Aaditya |
imported>Aaditya |
||
Line 73: | Line 73: | ||
== build-set == | == build-set == | ||
build-set is used to build a particular package or a set. The help looks like the following for x86_64 | |||
$ build-set -h | |||
Usage: build-set [options] -- [makepkg_args] | |||
-p <profile> Set profile or pkg [default: default] | |||
-a <arch> Set arch [default: x86_64] | |||
-b <branch> Set branch [default: stable] | |||
-r <dir> Chroots directory [default: /srv/manjarobuild] | |||
-c Clean chroot | |||
-w Wipe clean pkgbuild and pkg directory | |||
-n Run namcap check | |||
-s Sign packages | |||
-q Query settings and pretend build | |||
-h This help | |||
To build a single package, for example upower-pm-utils, go into the package build directory (which contains the PKGBUILD), and run it as: | |||
sudo build-set -p upower-pm-utils |
Revision as of 04:51, 7 November 2014
Introduction
manjaro-tools is a replacement for devtools. It consists of two componenets, the devtools and arch-install-scripts, but manjarobuild and its symlinks got replaced by build-set.
Configuration
manjaro-tools can be configured via editing /etc/manjaro-tools/manjaro-tools.conf
Files
These are the new names for renamed scripts.
- mkmanjaroroot --> mkchroot
- manjarobuild --> build-set
- pacstrap --> basestrap
- genfstab --> fstabgen
- arch-chroot --> manjaro-chroot
- make-set
Tools
make-set
build-set features building from build lists as well as single packages.
Build lists can be defined in /etc/manjaro-tools/sets/<buildlistname>.set
To create a build list, one can run in the pkgbuilds/abs dir:
sudo make-set -c <name>
This will create a build list containing all directories with PKGBUILDs in them. This generated list can be then edited, like packages can be removed.
For example, in a git clone of https://github.com/udeved/pkgbuilds
$ ls consolekit manjaro-openrc openrc-net eudev manjaro-tools packages eudev-systemdcompat networkmanager-openrc polkit-consolekit kde-servicemenus-pkg-tools openrc-aur README.md keyboardctl-openrc openrc-base sddm-consolekit kf5-servicemenus-pkg-tools openrc-desktop sysvinit lib32-eudev openrc-devel upower-pm-utils lib32-eudev-systemdcompat openrc-misc
Running sudo make-set -c openrc does
$ sudo make-set -c openrc [sudo] password for aaditya: ==> Creating [/etc/manjaro-tools/sets/openrc.set] ... -> Adding consolekit -> Adding eudev -> Adding eudev-systemdcompat -> Adding kde-servicemenus-pkg-tools -> Adding keyboardctl-openrc -> Adding kf5-servicemenus-pkg-tools -> Adding lib32-eudev -> Adding lib32-eudev-systemdcompat -> Adding manjaro-openrc -> Adding manjaro-tools -> Adding networkmanager-openrc -> Adding openrc-aur -> Adding openrc-base -> Adding openrc-desktop -> Adding openrc-devel -> Adding openrc-misc -> Adding openrc-net -> Adding polkit-consolekit -> Adding sddm-consolekit -> Adding sysvinit -> Adding upower-pm-utils
build-set
build-set is used to build a particular package or a set. The help looks like the following for x86_64
$ build-set -h Usage: build-set [options] -- [makepkg_args] -p <profile> Set profile or pkg [default: default] -a <arch> Set arch [default: x86_64] -b <branch> Set branch [default: stable] -r <dir> Chroots directory [default: /srv/manjarobuild] -c Clean chroot -w Wipe clean pkgbuild and pkg directory -n Run namcap check -s Sign packages -q Query settings and pretend build -h This help
To build a single package, for example upower-pm-utils, go into the package build directory (which contains the PKGBUILD), and run it as:
sudo build-set -p upower-pm-utils