Difference between revisions of "Buildiso with AUR packages: Using buildpkg"
Buildiso with AUR packages: Using buildpkg (view source)
Revision as of 21:57, 11 May 2015
, 9 years ago→Example:
imported>Excalibur1234 |
imported>Excalibur1234 |
||
| Line 188: | Line 188: | ||
profile.conf | profile.conf | ||
You can have both <code>pacman-multilib.conf</code> and <code>pacman-default.conf</code> files in your profile directory. The <code>pacman-default.conf</code> file will get used by ''buildiso'' to build 32bit ISOs and <code>pacman-multilib.conf</code> will get used for 64bit ISOs. | |||
Your new <code>pacman-multilib.conf</code> file looks like this: | |||
# | # | ||
| Line 294: | Line 296: | ||
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 <code>[local-repo]</code> in this tutorial). Packages neither available in the Manjaro repositories nor in the AUR are best installed from a custom non-local repository (see <code>[infinality-bundle]</code> as example). | 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 <code>[local-repo]</code> in this tutorial). Packages neither available in the Manjaro repositories nor in the AUR are best installed from a custom non-local repository (see <code>[infinality-bundle]</code> as example). | ||
==7. Add package names to ISO profile== | ==7. Add package names to ISO profile== | ||