Manjaro Difference between pages "Download Manjaro" and "Manjaro-tools"

Difference between pages "Download Manjaro" and "Manjaro-tools"

From Manjaro
(Difference between pages)
imported>Verityproductions
 
imported>Aaditya
 
Line 1: Line 1:
== Downloading the ISO image ==
= Introduction =


*Download the Manjaro Linux ISO with your favorite desktop environment [KDE, GNOME, XFCE] from our [http://sourceforge.net/projects/manjarolinux/files/release/ SourceForge page.]
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.


*You can also download our latest releases through the '''BitTorrent protocol'''. This option usually provides faster download speeds and it also helps reducing our hoster's bandwidth consumption. To download through this method, you will have to install a BitTorrent application. The most common would be: µTorrent, Transmission, Deluge, Azureus. So, if you've set up your BitTorrent client, go an [http://linuxtracker.org/index.php?page=torrents&search=manjaro&category=0&active=1&tracker=0 grab a torrent] of your favorite Manjaro Linux flavor. 
= Configuration =


You will find x86 and x86-64 ISO images, make sure you download the appropriate one for your hardware.
manjaro-tools can be configured via editing {{ic|''/etc/manjaro-tools/manjaro-tools.conf''}}


== Writing the ISO image to a CD/DVD ==
= Files =


{{note| If you intend to install Manjaro to a virtual machine using Oracle's Virtualbox, it will not be necessary to burn the ISO to a CD/DVD or USB flash drive. Virtualbox is able to read and install from ISO files directly.}}
These are the new names for renamed scripts.


===== Burning the ISO to a CD/DVD from Microsoft Windows. =====
*    mkmanjaroroot --> mkchroot
*    manjarobuild --> build-set
*    pacstrap --> basestrap
*    genfstab --> fstabgen
*    arch-chroot --> manjaro-chroot
*    make-set


For burning the ISO from the Microsoft Windows Operating System you can use the free [http://cdburnerxp.se/en/download CDBurnerXP] tool.
= Tools =


===== Burning the ISO to a CD/DVD from Linux =====
== make-set ==


For burning the ISO from a Linux based Operating System you can use ''Xfburn, K3b, Brasero Disk Burner'', and many others. These are usually found in your current distro's repositories, and sometimes, they come pre installed with the system.
build-set features building from build lists as well as single packages.
Build lists can be defined in {{ic|/etc/manjaro-tools/sets/<buildlistname>.set}}


To create a build list, one can run in the pkgbuilds/abs dir:


== Writing the ISO image to a USB flash drive ==
sudo make-set -c <name>


===== From Windows =====
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.


You can use the free and open source tool [https://launchpad.net/win32-image-writer Win32 Disk Imager]. Run it and select the right USB drive, then browse for your Manjaro Linux ISO. Note: Win32 Disk Imager assumes that image files have the " .img " extension, because of that you will most likely be unable to see your ISO unless you do a tweak. When browsing for the image, at the bottom, replace the extensions with " *.iso* ". That way you will be able to see and select your ISO image.
For example, in a git clone of https://github.com/udeved/pkgbuilds


===== From Linux based Operating Systems =====
$ 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


{{Warning|This will destroy all data on your USB drive.}}
Running '''sudo make-set -c openrc''' does


1. First, format your USB drive with FAT32 using your favorite tool, like GParted.
$ 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


2. Using " lsblk ", make sure your USB drive is '''unmounted''', and make sure your use '''''/dev/sdx''''' instead of '''''/dev/sdx1'''''.
{{Note|The set name should be different from a directory name in abs dir. Anything else should work, eg adding a date to the name.}}


3. Change directory to your ISO location (Example):
== build-set ==
{{term|# cd /home/username/downloads/}}


4. Then run the following command:
build-set is used to build a particular package or a set. The help looks like the following for x86_64
{{term|1=# dd if=name_of_the_iso.iso of=/dev/sdx bs=4M}}


The process will take a few minutes, depending on the size of the image and your hardware.
$ build-set -h
{{Note|It will not show the progress, it will show a message only after the process is finished.}}
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


[[Category:Getting Started]]
To build a single package, for example upower-pm-utils, go into the directory which is one above the package build directory (which contains the PKGBUILD), and run it as:
[[Category:Contents Page]]
 
sudo build-set -p <package-name>
 
For example,
 
$ ls
consolekit                  manjaro-tools          openrc-video
eudev                      networkmanager-openrc  packages
eudev-systemdcompat        openrc-aur            polkit-consolekit
kde-servicemenus-pkg-tools  openrc-base            README.md
keyboardctl-openrc          openrc-core            sddm-consolekit
kf5-servicemenus-pkg-tools  openrc-desktop        sysvinit
lib32-eudev                openrc-devel          upower-pm-utils
lib32-eudev-systemdcompat  openrc-misc
manjaro-openrc              openrc-net
 
$ sudo build-set -p upower-pm-utils
==> manjaro-tools version: 0.9.1
==> OPTARGS:
  -> arch: x86_64
  -> branch: testing
  -> chroots: /srv/manjarobuild
==> PATHS:
  -> chrootdir: /srv/manjarobuild/testing/x86_64
  -> profiledir: /etc/manjaro-tools/sets
  -> pkgdir: /var/cache/manjaro-tools/pkg/testing/x86_64
  -> pacman_conf: /usr/share/manjaro-tools/pacman-default.conf
  -> makepkg_conf: /usr/share/manjaro-tools/makepkg-x86_64.conf
==> SETS:
  -> profiles: default|nosystemd|openrc-artoo|openrc-nodeps|openrc|udev
  -> profile: consolekit
  -> is_profile: false
==> This package will be built:
  -> consolekit
==> Updating chroot for [testing] (x86_64)...
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do
==> Making package: upower-pm-utils 0.9.23-3 (Fri Nov 14 15:54:02 UTC 2014)
...
...
...
==> Finished making: upower-pm-utils 0.9.23-3 (Fri Nov 14 15:54:18 UTC 2014)
  -> Moving [upower-pm-utils] to [/var/cache/manjaro-tools/pkg/testing/x86_64]
==> chown -R [aaditya:users] [/var/cache/manjaro-tools/pkg/testing]

Revision as of 16:01, 14 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


Note
The set name should be different from a directory name in abs dir. Anything else should work, eg adding a date to the name.

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 directory which is one above the package build directory (which contains the PKGBUILD), and run it as:

sudo build-set -p <package-name>

For example,

$ ls
consolekit                  manjaro-tools          openrc-video
eudev                       networkmanager-openrc  packages
eudev-systemdcompat         openrc-aur             polkit-consolekit
kde-servicemenus-pkg-tools  openrc-base            README.md
keyboardctl-openrc          openrc-core            sddm-consolekit
kf5-servicemenus-pkg-tools  openrc-desktop         sysvinit
lib32-eudev                 openrc-devel           upower-pm-utils
lib32-eudev-systemdcompat   openrc-misc
manjaro-openrc              openrc-net
$ sudo build-set -p upower-pm-utils
==> manjaro-tools version: 0.9.1
==> OPTARGS:
 -> arch: x86_64
 -> branch: testing
 -> chroots: /srv/manjarobuild
==> PATHS:
 -> chrootdir: /srv/manjarobuild/testing/x86_64
 -> profiledir: /etc/manjaro-tools/sets
 -> pkgdir: /var/cache/manjaro-tools/pkg/testing/x86_64
 -> pacman_conf: /usr/share/manjaro-tools/pacman-default.conf
 -> makepkg_conf: /usr/share/manjaro-tools/makepkg-x86_64.conf
==> SETS:
 -> profiles: default|nosystemd|openrc-artoo|openrc-nodeps|openrc|udev
 -> profile: consolekit
 -> is_profile: false
==> This package will be built:
 -> consolekit
==> Updating chroot for [testing] (x86_64)...
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do
==> Making package: upower-pm-utils 0.9.23-3 (Fri Nov 14 15:54:02 UTC 2014)
...
...
...
==> Finished making: upower-pm-utils 0.9.23-3 (Fri Nov 14 15:54:18 UTC 2014)
 -> Moving [upower-pm-utils] to [/var/cache/manjaro-tools/pkg/testing/x86_64]
==> chown -R [aaditya:users] [/var/cache/manjaro-tools/pkg/testing]
Cookies help us deliver our services. By using our services, you agree to our use of cookies.