Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<languages/>
__TOC__

<div lang="en" dir="ltr" class="mw-content-ltr">
This tutorial is about creating your own online repository and building a custom package(set) with the help of ''buildpkg''. Later, you can install those packages to your customized Manjaro ISO using '''buildiso'''.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Before you start with this tutorial make sure you have completed the prerequisite steps in [[Build Manjaro ISOs with buildiso]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The same XFCE ISO profile will be used as example on this Wiki page.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Tools to install==
Sync your system with the latest packages and ensure you have the following packages installed.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* git
* manjaro-tools-{base|base-git}
* manjaro-tools-{pkg|pkg-git}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is important that you match your tools packages - don't mix the default and git packages.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Create directories==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The first thing you should probably do is create a directory for your online repository. The online repository is called '''online-repo''' throughout this tutorial and it is located in your home-folder. You however are free to choose name location to your liking. This'll help keep things organized. Your repository consist of only this folder:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mkdir ~/online-repo/x86_64}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This online repository is created in your home folder, but you can create it anywhere you want.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Create your custom package tree==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Create a folder for the packages you want to build. The name is arbitrary decriptor - you can call it anything you think suitable.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mkdir ~/pkgbuild}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Clone the relevant package(s) from AUR or from Github. Later you might create them yourself! You can select any package to build but as example we build the package <code>kickshaw</code>. Kickshaw is modern menu editor for among others openbox. First you add it to your pkgubild repo. Do this using git
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=cd ~/pkgbuild}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Clone the example package from AUR
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=git clone <nowiki>https://aur.archlinux.org/kickshaw</nowiki>}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now you have a folder with a <code>PKGBUILD</code> file in your pkgbuild repository.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=ls -R ~/pkgbuild}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is best practice to always familarize yourself with the content of the package to ensure everything is as expected.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Building with buildpkg==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The '''buildpkg''' has some options you need to familiarize yourself with.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{File|file=buildpkg -h|content=<pre>
Usage: buildpkg [options]
   -p <pkg>           Build list or pkg [default: default]
   -a <arch>          Arch [default: x86_64]
   -b <branch>        Branch [default: unstable]
   -r <dir>           Chroots directory
                      [default: /var/cache/manjaro-tools]
   -i <pkgs>          Install packages into the working copy of the chroot
   -c                 Recreate chroot
   -w                 Clean up cache and sources
   -n                 Install and run namcap check
   -s                 Sign packages
   -u                 Udev base-devel group (no systemd)
   -q                 Query settings and pretend build
   -h                 This help
</pre>}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Next thing to do is build the package. Please note that you must be located one level above your actual PKGBUILD. Understand this as the <code>-p</code> argument is '''the name of the folder''' holding the PKGBUILD instructionset.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=buildpkg -p kickchaw}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For more examples how to use '''buildpkg''', look [https://wiki.manjaro.org/index.php?title=Manjaro-tools#buildpkg here].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The buildpkg script creates a closed environment for building the package. This is done, so not to pollute your system with build artifacts.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Copy package files to online repository==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The resulting package is saved in the location defined in your manjaro-tools.conf on your system (default is the cache folder)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=ls /var/cache/manjaro-tools/pkg/stable/x86_64}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You should see compressed package files. The file name should end with <code>.pkg.tar.zst</code>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Copy or move your package files to your online repository:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=mv /var/cache/manjaro-tools/pkg/stable/x86_64 ~/online-repo}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Build a .db file==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To keep track of available packages the ''pacman'' package manager uses database files which is downloaded and kept on your computer. You need to create such a database file for your repo. It is crucial that your database filename is the same as your repo name. If your repo is named '''online-repo''' then your database name must be '''online-repo.db.tar.gz'''.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Use the command <code>repo-add</code> to build a database file inside your designated repo folder
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=cd ~/online-repo/x86_64}}
{{UserCmd|command=repo-add online-repo.db.tar.gz *.pkg.tar.*}}
{{File|file=~/online-repo/x86_64|content=<pre>
kickshaw-0.5-2-x86_64.pkg.tar.zst
online-repo.db
online-repo.db.tar.gz
online-repo.files
online-repo.files.tar.gz
</pre>}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Every time you change the content of your online repository, the database must be rebuild! Otherwise, ''buildiso'' will complain later about missing packages in your online repository.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Two of the files are symlinks which may or may not work on your chosen host so they can be left out.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Upload online-repo to Host Server==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now you need to upload online-repo to your Host Server. Upload everything from online-repo to your Host Server. Your web address as to match the name of the directory folder you created. This is what your web address should look like after upload online-repo to your Host Server.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<nowiki>http://www.myserver.com/repository/online-repo/x86_64/</nowiki>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Add online-repo to your iso-profile==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Create a file
{{File|file=${profile_dir}/user-repos.conf|content=<pre>
[online-repo]
SigLevel = Never
Server = <nowiki>http://www.myserver.com/repository/online-repo/$repo/$arch</nowiki></pre>}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Custom online repositories will be added to the resulting '''pacman.conf'''. This means AUR packages cannot be installed unless you are using webserver to provide <code>[online-repo]</code> as shown this article).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
NB: '''${profile_dir}''' is not the '''iso-profiles''' directory but the specific sub-directory for a build, e.g. '''iso-profiles/manjaro/kde'''. Put your file '''user-repos.conf''' there to be found during the build process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Add package names to ISO profile==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now you add <code>kickshaw</code> to your package list for your ISO profile. This means your '''Packages-Desktop''' file should look something like this:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{File|file=~/iso-profiles/manjaro/xfce/Packages-Desktop|content=<pre>
ffmpegthumbnailer
gconf # fix qt-theme
gnome-keyring # fix wlan segfault
gufw # firewall
accountsservice
lightdm-gtk-greeter
lightdm-gtk-greeter-settings
light-locker
manjaro-settings-manager
menulibre
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
## AUR packages
kickshaw</pre>}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Cleaning build environment==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For removing your build environment from your hard drive, execute:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo rm -r /var/lib/manjaro-tools/buildpkg}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now, you can continue to [https://wiki.manjaro.org/index.php?title=Build_Manjaro_ISOs_with_buildiso#manjaro-tools.conf adjust your manjaro-tools.conf] or [https://wiki.manjaro.org/index.php?title=Build_Manjaro_ISOs_with_buildiso#Build_your_ISO build your ISO].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Creating an online repo requires you to keep the repo up-to-date when changes are made upstream.
</div>
[[Category:Contents Page{{#translation:}}]]
[[Category:ISO{{#translation:}}]]
[[Category:Development{{#translation:}}]]