Manjaro

Buildiso with AUR packages: Using buildpkg

Revision as of 21:57, 11 May 2015 by imported>Excalibur1234


This tutorial is about creating your own local repository. This repository can be used to download (with the help of yaourt) and build (with the help of buildpkg) packages. Later, you can install those packages to your customized Manjaro ISO using buildiso.


Before you start with this tutorial make sure you have completed the prerequisite steps in Build Manjaro ISOs with buildiso.

The same XFCE ISO profile will be used as example on this Wiki page.


1. Create directories

The first thing you should probably do is create a directory for your local repository. The local repository is called local-repo throughout this entire tutorial. This'll help keep things organized. 

 mkdir -p ~/local-repo/

This local repository is created in your home folder, but you can create it anywhere you want.


Next, you need to create a build directory. During the course of this tutorial you will need it as a temporary directory for files from the AUR: 

 mkdir -p ~/local-build/

This temporary build directory is created in your home folder, but you can create it anywhere you want.


2. Download package files from AUR using yaourt

Now, go to your local repository: 

cd ~/local-build

Next do 

yaourt -G <package name>

in order to download package files from the AUR to your build directory. You will see a new directory with the package name. In it are various files, including a PKGBUILD file.

Example:

You want to add the package pcmanfm-qt-git to your ISO. Therefore, you need to download it to your local repository first. You download and unpack it using 

yaourt -G pcmanfm-qt-git

You see a new PKGBUILD file in your local repository: 

~/local-repo/pcmanfm-qt-git/PKGBUILD


3. Building with buildpkg

Up to this point, you have only downloaded and unpacked files from the AUR. Next, you need to build those files into proper packages: 

cd ~/local-build

buildpkg -p <package name>


If you want to build 32bit packages on a 64bit system, you can do this by specifying the architecture: 

buildpkg -a i686 -p <package name>


For more examples how to use buildpkg, look here.

Example:

As instructed above, try to build pcmanfm-qt-git: 

buildpkg -p pcmanfm-qt-git

The build get aborted with the following error message: 

==> Installing missing dependencies...
error: target not found: liblxqt-git
==> ERROR: 'pacman' failed to install missing dependencies.

This means liblxqt-git is a dependency of pcmanfm-qt-git. You need to download and build liblxqt-git before you can build pcmanfm-qt-git successfully. Therefore, do the same (with one slight difference) as you did with pcmanfm-qt-git: 

yaourt -G liblxqt-git
buildpkg -n -p liblxqt-git

Please note the additional -n argument. This argument installs liblxqt-git in your build environment (pcmanfm-qt-git needs liblxqt-git installed in order to utilize it).

Again, you receive an error: 

==> Installing missing dependencies...
error: target not found: libqtxdg-git
==> ERROR: 'pacman' failed to install missing dependencies.

So, liblxqt-git has another dependency: libqtxdg-git Repeat the whole process with libqtxdg-git: 

yaourt -G libqtxdg-git
buildpkg -n -p libqtxdg-git

Finally, a package gets build (and installed in your build environment) successfully!

Now, build the other packages (in reverse order): 

buildpkg -n -p liblxqt-git
buildpkg -p pcmanfm-qt-git


4. Copy package files to local repository

In the last chapter you build packages. These packages were created in this directory on your system: 

/var/cache/manjaro-tools/

On a 64bit system using the unstable branch the exact path is 

/var/cache/manjaro-tools/unstable/x86_64

You should see compressed package files. The file name should end with .pkg.tar.xz.


Move all package files to your local repository: 

~/local-repo/

Example:

Your local repository should now look like this: 

liblxqt-git-0.8.0.23.g079768e-1-x86_64.pkg.tar.xz  
libqtxdg-git-1.0.0.7.g0503cf7-1-x86_64.pkg.tar.xz  
pcmanfm-qt-git-0.8.0.4.g99987af-1-x86_64.pkg.tar.xz


5. Build a .db file

Use the command repo-add to build a database file. Run the following commands in a terminal: 

cd ~/local-repo/
repo-add local-repo.db.tar.gz *.pkg.tar.*
sudo pacman -Syy

Every time you add packages to your local repositories, these commands need to be executed again! Otherwise, buildiso will complain later about missing packages in your local repository.

Example:

After running those commands, your local repository looks like this: 

local-repo.db.tar
local-repo.db
liblxqt-git-0.8.0.23.g079768e-1-x86_64.pkg.tar.xz  
libqtxdg-git-1.0.0.7.g0503cf7-1-x86_64.pkg.tar.xz  
pcmanfm-qt-git-0.8.0.4.g99987af-1-x86_64.pkg.tar.xz


6. Add local-repo to pacman-XXXXX.conf file

Open your /etc/pacman.conf file. Attention: This file is different for 32bit and 64bit systems: On 64bit systems the [multilib] repository is included. Copy and save the entire content of /etc/pacman.conf to 

manjaro-tools-iso-profiles/xfce/pacman-XXXXX.conf

Replace pacman-XXXXX.conf with

  • pacman-default.conf if you have only 32bit packages in your local repository: Remove the [multilib] repository

from this file.

  • pacman-multilib.conf if you have only 64bit packages in your local repository: This file needs a [multilib] repository

At the bottom of the just created pacman-XXXXX.conf file, add: 

[local-repo]
SigLevel = Never
Server = file:///home/<username>/local-repo/

Replace <username> with your username.

Delete or add the [multilib] repository: 

[multilib]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

Example:

Your customized XFCE ISO profile should now look like this (for building 64bit ISOs): 

xfce-overlay
isolinux -> ../shared/isolinux/
mkinitcpio.conf -> ../shared/mkinitcpio.conf
overlay -> ../shared/overlay/
overlay-livecd -> ../shared/overlay-livecd/
Packages -> ../shared/Packages-Systemd
Packages-Livecd -> ../shared/Packages-Livecd-Systemd
Packages-Xfce
Packages-Xorg -> ../shared/Packages-Xorg
pacman-multilib.conf
profile.conf

You can have both pacman-multilib.conf and pacman-default.conf files in your profile directory. The pacman-default.conf file will get used by buildiso to build 32bit ISOs and pacman-multilib.conf will get used for 64bit ISOs.

Your new pacman-multilib.conf file looks like this: 

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
HoldPkg      = pacman glibc manjaro-system
# If upgrades are available for these packages they will be asked for first
SyncFirst    = manjaro-system
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
Color
#TotalDownload
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Manjaro Linux
# packagers with `pacman-key --populate archlinux manjaro`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[community]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

[multilib]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

#[infinality-bundle]
#SigLevel = Never
#Server = http://bohoomil.com/repo/$arch

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

[local-repo]
SigLevel = Never
Server = file:///home/excalibur/local-repo/

As you can see, there is also another custom repository in this pacman-multilib.conf file: [infinality-bundle]. But it is commented out. This illustrates nicely the way to add a custom non-local repository.

Custom local repositories will get removed automatically from this file before it gets copied over to the installed system, whereas custom non-local repositories will be kept. This means AUR packages are best installed from a custom local repository (as demonstrated by [local-repo] in this tutorial). Packages neither available in the Manjaro repositories nor in the AUR are best installed from a custom non-local repository (see [infinality-bundle] as example).


7. Add package names to ISO profile

Using the example mentioned in here, you can now add the AUR package names to your Packages-Xfce file.

Attention: You need to add all dependency names before the package name (only for dependencies from the AUR).

Example:

You can now add pcmanfm-qt-git to your package list for your ISO profile. This means your manjaro-tools-iso-profiles/xfce/Packages-Xfce file should look exactly like this: 

### Manjaro Packages

## XFCE Main Packages
ffmpegthumbnailer
gconf                    # fix qt-theme
gnome-keyring            # fix wlan segfault
gufw                     # firewall
# mdm-themes
accountsservice
lightdm-gtk-greeter
lightdm-gtk-greeter-settings
light-locker
manjaro-settings-manager
>i686 gcc
>x86_64 gcc-multilib

...

## AUR packages
local-repo/libqtxdg-git
local-repo/liblxqt-git 
local-repo/pcmanfm-qt-git

The order of package installations to your ISO is from top to bottom. Please note the exact order of the last 3 packages. pcmanfm-qt-git depends on liblxqt-git, which depends on libqtxdg-git (see chapter 4.1). Therefore, liblxqt-git needs to be the first package, which gets installed!


More

Just to be sure, let's do another 

sudo pacman -Syy

You should see your new local-repo in the list of repositories getting synchronized (next to these repositories: core, extra, community, and multilib - only on 64bit systems).


Now, you can continue to adjust your manjaro-tools.conf or build your ISO.


Please remember to install yaourt, octopi, or pamac on your ISO, too. Only these Programs can update packages from the AUR.

Retrieved from "https://wiki.manjaro.org/index.php?title=Buildiso_with_AUR_packages:_Using_buildpkg&oldid=3014"