Alpine Linux - User contributions [en]

User:OxR463/Drafts/installation on android

2019-02-13T00:54:17Z

OxR463: /* Setup Disk */

== Dependencies ==

* Root Access

* Busybox

* ADB / Terminal Emulator

== Setup Disk ==

=== File Structure ===

<pre>
/data/data/org.alpinelinux/
├── cache
│ └── alpine-minirootfs-3.9.0-aarch64.tar.gz
└── files
└── rootfs.bin

2 directories, 2 files
</pre>

=== Virtual Disk Creation ===

{{Cmd|fallocate -l 1G rootfs.bin}}

=== Encryption via LUKS ===

{{Cmd|cryptsetup luksFormat rootfs.bin}}

For more on this, see [https://wiki.alpinelinux.org/wiki/LVM_on_LUKS LVM on LUKS].

=== Format File System ===

{{Cmd|cryptsetup luksOpen rootfs.bin alpine}}

{{Cmd|mkfs.ext4 /dev/mapper/alpine}}

== Bootstrap System ==

* Fetch File System Tarball

* Chroot

== Further Configuration ==

* TODO

== Helper Scripts ==

* TODO

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-13T00:38:43Z

OxR463: /* Dependencies */

== Dependencies ==

* Root Access

* Busybox

* ADB / Terminal Emulator

== Setup Disk ==

<pre>
/data/data/org.alpinelinux/
├── cache
│ └── alpine-minirootfs-3.9.0-aarch64.tar.gz
└── files
└── rootfs.bin

2 directories, 2 files
</pre>

{{Cmd|fallocate -l 1G rootfs.bin}}

* Encrypt via LUKS

* Mount

* Format File System

== Bootstrap System ==

* Fetch File System Tarball

* Chroot

== Further Configuration ==

* TODO

== Helper Scripts ==

* TODO

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-13T00:25:40Z

OxR463: /* Setup Disk */

== Dependencies ==

* Root Access

* Busybox

* ADB / Termux or other Shell

== Setup Disk ==

<pre>
/data/data/org.alpinelinux/
├── cache
│ └── alpine-minirootfs-3.9.0-aarch64.tar.gz
└── files
└── rootfs.bin

2 directories, 2 files
</pre>

{{Cmd|fallocate -l 1G rootfs.bin}}

* Encrypt via LUKS

* Mount

* Format File System

== Bootstrap System ==

* Fetch File System Tarball

* Chroot

== Further Configuration ==

* TODO

== Helper Scripts ==

* TODO

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-13T00:22:52Z

OxR463: /* Setup Disk */

== Dependencies ==

* Root Access

* Busybox

* ADB / Termux or other Shell

== Setup Disk ==

<code>
/data/data/org.alpinelinux/
├── cache
│ └── alpine-minirootfs-3.9.0-aarch64.tar.gz
└── files
└── rootfs.bin

2 directories, 2 files
</code>

{{Cmd|fallocate -l 1G rootfs.bin}}

* Encrypt via LUKS

* Mount

* Format File System

== Bootstrap System ==

* Fetch File System Tarball

* Chroot

== Further Configuration ==

* TODO

== Helper Scripts ==

* TODO

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-12T03:22:13Z

OxR463:

== Dependencies ==

* Root Access

* Busybox

* ADB / Termux or other Shell

== Setup Disk ==

{{Cmd|fallocate -l 1G rootfs.bin}}

<code>/data/data/org.alpinelinux/</code>

* Encrypt via LUKS

* Mount

* Format File System

== Bootstrap System ==

* Fetch File System Tarball

* Chroot

== Further Configuration ==

* TODO

== Helper Scripts ==

* TODO

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-12T03:21:28Z

OxR463:

== Setup Disk ==

{{Cmd|fallocate -l 1G rootfs.bin}}

<code>/data/data/org.alpinelinux/</code>

* Encrypt via LUKS

* Mount

* Format File System

== Bootstrap System ==

* Fetch File System Tarball

* Chroot

== Further Configuration ==

* TODO

== Helper Scripts ==

* TODO

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-12T03:16:24Z

OxR463: /* Create Virtual Disk */

== Create Virtual Disk ==

{{Cmd|fallocate -l 1G rootfs.bin}}

<code>/data/data/org.alpinelinux/</code>

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-12T03:15:40Z

OxR463:

== Create Virtual Disk ==

{{Cmd|fallocate -l 1G rootfs.bin}}

/data/data/org.alpinelinux/

== References ==

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-12T03:14:56Z

OxR463: /* Create Virtual Disk */

== Create Virtual Disk ==

fallocate -l 1G rootfs.bin

/data/data/org.alpinelinux/

* [https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]
* [https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]

User:OxR463/Drafts/installation on android

2019-02-12T03:14:44Z

OxR463: Created page with "== Create Virtual Disk == fallocate -l 1G rootfs.bin /data/data/org.alpinelinux/ * https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and fil..."

== Create Virtual Disk ==

fallocate -l 1G rootfs.bin

/data/data/org.alpinelinux/

* [[https://developer.android.com/guide/topics/data/data-storage#filesInternal Data and file storage overview | Android Developers]]
* [[https://developer.android.com/google/play/expansion-files APK Expansion Files | Android Developers]]

User:OxR463

2019-02-12T02:53:25Z

OxR463:

<elitist>the command line is all you need anyway</elitist>

== Articles ==

* [[/Drafts/installation_on_android|Installation On Android]]

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/oxr463/aports Aports Development Fork]
* [https://gitlab.com/oxr463/overlay Ebuild Overlay]
* [https://www.funtoo.org/User:Rage Funtoo Wiki]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@protonmail.com Repology]
* [http://lramage.gitlab.io Website]

== Links ==
* [https://wiki.alpinelinux.org/wiki/Creating_patches Creating Patches]
* [https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package Creating Alpine Packages]

User:OxR463

2019-02-12T00:47:03Z

OxR463: /* External */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/oxr463/aports Aports Development Fork]
* [https://gitlab.com/oxr463/overlay Ebuild Overlay]
* [https://www.funtoo.org/User:Rage Funtoo Wiki]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@protonmail.com Repology]
* [http://lramage.gitlab.io Website]

== Links ==
* [https://wiki.alpinelinux.org/wiki/Creating_patches Creating Patches]
* [https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package Creating Alpine Packages]

User:OxR463

2018-12-13T01:37:02Z

OxR463: /* Links */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [https://www.funtoo.org/User:Rage Funtoo Wiki]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

== Links ==
* [https://wiki.alpinelinux.org/wiki/Creating_patches Creating Patches]
* [https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package Creating Alpine Packages]

User:OxR463

2018-08-23T16:15:58Z

OxR463: /* Wiki */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [https://www.funtoo.org/User:Rage Funtoo Wiki]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

== Links ==
* [https://wiki.alpinelinux.org/wiki/Creating_patches Creating Patches]

User:OxR463

2018-08-23T16:12:59Z

OxR463:

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [https://www.funtoo.org/User:Rage Funtoo Wiki]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

== Wiki ==
* [https://wiki.alpinelinux.org/wiki/Creating_patches Creating Patches]

Writing Init Scripts

2018-07-26T14:54:46Z

OxR463: /* Introduction */ fix typos

{{Draft}}

== Introduction ==

Alpine Linux uses the [https://github.com/OpenRC/openrc OpenRC] init system to start services. Don't confuse OpenRC init with our system init (the first process that is executed aka pid 1). Many of the current init.d script found in Alpine Linux are taken from Gentoo. If you want to save time you could search [https://packages.gentoo.org/categories Gentoo's repository] for an existing initscript for your service. You can also check [https://wiki.gentoo.org/wiki/Handbook:X86/Working/Initscripts#Writing_initscripts Gentoo's wiki] for some additional OpenRC information.

NOTE: OpenRC recently added [https://github.com/OpenRC/openrc/blob/master/service-script-guide.md documentation] on how to write proper Init scripts. Make sure you read it!

If you cannot find an init.d script from Gentoo, or you just want to start to write your own init.d scripts, we provide you with some basic information on how to write simple OpenRC init scripts.

Primary information about the OpenRC format can be found in the [http://manpages.org/openrc-run/8 OpenRC man page openrc-run].

<code>apk add openrc-doc man</code>

<code>man openrc-run</code>

== Minimal Templates ==

Every init.d script you write needs to start with a [https://en.wikipedia.org/wiki/Shebang_(Unix) shebang] like:

<code>#!/sbin/openrc-run</code>

=== Services relying on OpenRC exclusively ===

<pre>
#!/sbin/openrc-run

command="/path/to/command"
</pre>

=== Services supervised by [http://www.skarnet.org/software/s6/ s6] ===

Notes:

* Install and configure the <code>s6-scan</code> service to start on system boot
* Exclude <code>start()</code>, <code>stop()</code> and <code>status()</code> functions in order for s6 supervision to work reliably. OpenRC has built-in equivalent functions which invoke the necessary s6 commands.
* Include a <code>depend()</code> stanza to ensure that the <code>s6-svscan</code> service is already running.
* Add a <code>start_pre()</code> stanza to symlink the service directory into the scan directory, because the <code>/etc/init.d/bootmisc</code> scripts cleans out the <code>/run</code> directory on system boot.

<pre>
#!/sbin/openrc-run

name="foo"
supervisor="s6"
s6_service_path="${RC_SVCDIR}/s6-scan/${name}"

depend() {
need s6-svscan
}

start_pre() {
if [ ! -L "${RC_SVC_DIR}/s6-scan/${name}" ]; then
ln -s "/path/to/${name}/service/dir" "${RC_SVCDIR}/s6-scan/${name}"
fi
}
</pre>

The rest of the below basic example could be omitted, but that would most probably leave you with an non working initd script.

== Basic example ==

<pre>
#!/sbin/openrc-run

name=$RC_SVCNAME
cfgfile="/etc/$RC_SVCNAME/$RC_SVCNAME.conf"
command="/usr/bin/my_daemon"
command_args="--my-daemon-args"
command_user="my_system_user"
pidfile="/run/$RC_SVCNAME/$RC_SVCNAME.pid"
start_stop_daemon_args="--args-for-start-stop-daemon"
command_background="yes"

depend() {
need net
}

start_pre() {
checkpath --directory --owner $command_user:$command_user --mode 0775 \
/run/$RC_SVCNAME /var/log/$RC_SVCNAME
}
</pre>

== start, stop, restart functions ==

OpenRC defined a few basic functions ie: start, stop, restart. These functions are defined by default but can be overwritten by defining your own set of functions.
This is generally only necessary if you want to do something special which is not provided by the default start/stop/restart implementations.

=== start ===

<pre>
start() {
ebegin "Starting mydaemon"
start-stop-daemon --start \
--exec /usr/sbin/mydaemon \
--pidfile /var/run/mydaemon.pid \
-- \
--args-for-mydaemon
eend $?
}
</pre>

=== stop ===

=== restart ===

== Daemon, Forking, Logging ==

TODO...

[[Category:Booting]]

User:OxR463

2018-06-29T16:41:44Z

OxR463: /* External */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [https://www.funtoo.org/User:Rage Funtoo Wiki]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-23T21:44:19Z

OxR463: /* Work In Progress */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-23T21:43:57Z

OxR463: /* testing/festival */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-23T21:43:02Z

OxR463: /* Work In Progress */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/tree/testing/festival testing/festival] ====

Festival Speech Synthesis System

http://festvox.org/festival

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

==== [https://gitlab.com/lramage94/aports/tree/testing/usbguard testing/usbguard] ====

A USB device whitelisting tool

https://usbguard.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-23T21:39:46Z

OxR463: /* Packages */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

=== Current ===

These are the packages that I currently maintain.

==== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ====

Command-line tab-completion for bash

https://github.com/scop/bash-completion

==== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ====

Embeddable Common Lisp

https://common-lisp.net/project/ecl

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ====

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ====

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

==== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ====

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

=== Work In Progress ===

These are packages I am slowly working on adding.

==== [https://gitlab.com/lramage94/aports/issues/3 testing/pocketsphinx] ====

Speaker-independent large vocabulary continuous speech recognizer

https://cmusphinx.github.io

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-21T15:05:36Z

OxR463: /* External */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

These are the packages that I currently maintain.

=== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ===

Command-line tab-completion for bash

https://github.com/scop/bash-completion

=== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ===

Embeddable Common Lisp

https://common-lisp.net/project/ecl

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ===

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ===

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ===

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-19T19:10:44Z

OxR463: /* Packages */

<elitist>the command line is all you need anyway</elitist>

== [https://pkgs.alpinelinux.org/packages Packages] ==

These are the packages that I currently maintain.

=== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ===

Command-line tab-completion for bash

https://github.com/scop/bash-completion

=== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ===

Embeddable Common Lisp

https://common-lisp.net/project/ecl

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ===

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ===

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ===

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-19T14:58:08Z

OxR463: /* Packages */

<elitist>the command line is all you need anyway</elitist>

== Packages ==

These are the packages that I currently maintain.

=== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ===

Command-line tab-completion for bash

https://github.com/scop/bash-completion

=== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ===

Embeddable Common Lisp

https://common-lisp.net/project/ecl

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ===

Linux user-space application to modify the Intel Extensible Firmware Interface

https://github.com/rhboot/efibootmgr

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ===

Tools and library to manipulate EFI variables

https://github.com/rhboot/efivar

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ===

The most comprehensive testing and benchmarking platform available for Linux

https://www.phoronix-test-suite.com

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-19T14:57:26Z

OxR463: /* Packages */

<elitist>the command line is all you need anyway</elitist>

== Packages ==

These are the packages that I currently maintain.

=== [https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion main/bash-completion] ===

Command-line tab-completion for bash

HOMEPAGE: https://github.com/scop/bash-completion

=== [https://git.alpinelinux.org/cgit/aports/tree/community/ecl community/ecl] ===

Embeddable Common Lisp

HOMEPAGE: https://common-lisp.net/project/ecl

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr testing/efibootmgr] ===

Linux user-space application to modify the Intel Extensible Firmware Interface

HOMEPAGE: https://github.com/rhboot/efibootmgr

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/efivar testing/efivar] ===

Tools and library to manipulate EFI variables

HOMEPAGE: https://github.com/rhboot/efivar

=== [https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite testing/phoronix-test-suite] ===

The most comprehensive testing and benchmarking platform available for Linux

HOMEPAGE: https://www.phoronix-test-suite.com

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-19T13:47:17Z

OxR463:

<elitist>the command line is all you need anyway</elitist>

== Packages ==

* https://git.alpinelinux.org/cgit/aports/tree/main/bash-completion
* https://git.alpinelinux.org/cgit/aports/tree/community/ecl
* https://git.alpinelinux.org/cgit/aports/tree/testing/efibootmgr
* https://git.alpinelinux.org/cgit/aports/tree/testing/efivar
* https://git.alpinelinux.org/cgit/aports/tree/testing/phoronix-test-suite

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://repology.org/metapackages/by-maintainer/ramage.lucas@openmailbox.org Repology]
* [http://lramage94.gitlab.io Website]

User:OxR463

2018-06-10T20:22:11Z

OxR463:

User:OxR463

2018-06-08T16:01:14Z

OxR463:

<elitist>the command line is all you need anyway</elitist>

== External ==
* [https://gitlab.com/lramage94/aports Aports Development Fork]
* [https://gitlab.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://gitlab.com/lramage94 Gitlab]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://lramage94.gitlab.io Website]

File:Alogo 64x64.png

2018-05-16T15:44:33Z

OxR463:

Creating an Alpine package

2018-01-30T04:37:10Z

OxR463: /* pkgrel */

== Requirements ==

To build a package for Alpine Linux you need an Alpine Linux installation. Check the [[Installation]] page to see all available installation options.

== Setup your system and account ==
{{:Include:Setup_your_system_and_account_for_building_packages}}

== Getting some help ==

It might be wise to start by checking what the [[Abuild|abuild]] program can/cannot do.

{{Cmd|abuild -h}}

== Creating an APKBUILD file ==

=== Use a template APKBUILD ===

To create the actual APKBUILD file {{Pkg|newapkbuild}} can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.

If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.

{{:Include:Newapkbuild}}

{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}

[[Abuild_and_Helpers#apkbuild-cpan|apkbuild-cpan]] simplifies the creation of perl packages from CPAN and [[Abuild_and_Helpers#apkbuild-pypi|apkbuild-pypi]] ease the generation of APKBUILD files for python packages from PyPi.

If you are create a daemon package which needs initd scripts you can add the -c making it:

{{Cmd|newapkbuild -c ''packagename''}}

This will copy the sample initd and confd files to the build directory. 
A third file sample.install file will be copied as well (we will discuss this later on).

=== Modify your APKBUILD ===
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source).

If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like:

"$pkgdir"/somedir

This will prevent issues with spaces/special characters in the future.

{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}

=== APKBUILD variables/functions ===

==== source ====

The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.

Here are few things to note:

* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:
: {{cmd|abuild checksum}}
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}

* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre>
: (or similar depending on the package).

* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:
: <pre>http://oss.example.org/?get=software&ver=1.0</pre>
: You must prepend '${pkgname}-${pkgver}.tar.gz::' to the protocol, like so:
: <pre>source="${pkgname}-${pkgver}.tar.gz::http://oss.example.org/?get=software&ver=1.0"</pre>
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.

* Some projects didn't provide a release tarball. Beware that some git services (gitweg, cgit, …?) doesn’t provide ''stable'' tarballs, so when you point source to an tarball like <tt>http://repo.or.cz/w/gitstats.git/snapshot/ad7efbb9399e60cee6cb217c6b47e604174a8093.tar.gz</tt>, then you will run into issues because the checksum changes when downloading on the build system. This is not a problem on GitHub, GitLab and other decent services provides, they provide ''stable'' tarballs.

* abuild currently supports the following protocols for remote file retrieval:
** http
** https
** ftp



* abuild currently supports the following archive types/archive file extensions:
** .tar.gz / .tgz
** .tar.bz2
** .tar.lzma
** .tar.xz
** .zip

==== depends & makedepends ====

Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package, in depends you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [http://en.wikipedia.org/wiki/Rtfm RTFM].

No kidding, lots of important information can be found it the package INSTALL and README file (or the likes). Another good way is the run <code>./configure --help</code> from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a source directory you can create one with the command:

{{Cmd|abuild unpack}}

Running <code>configure</code> will also show you how you can disable a specific option for this package. A good example is for instance "--disable-nls" which will disable native language support and thus does not depend on gettext (libiconv, glib, ...).

Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided the package builder but please try to follow Alpine's design concept as much as possible.

An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo Linux ebuilds (previous versions of Alpine were based on Gentoo).

* [https://gitweb.gentoo.org/repo/gentoo.git/tree/ Gentoo Ebuilds]
* [http://www.archlinux.org/packages/search/ Arch Linux packages] [https://aur.archlinux.org/ Arch Linux User Repository]

After the package is successfully compiled and created we should make sure it didn't link to any package that is not present in the <code>$depends</code> variable. We do this by using <code>scanelf</code>. If scanelf is not yet installed on your system you can do that by installing {{Pkg|pax-utils}}.

{{Cmd|scanelf -nR pkg}}

An example output of {{Pkg|libcurl}} would be:

ET_DYN libssl.so.0.9.8,libcrypto.so.0.9.8,libz.so.1,libc.so.0,ld-uClibc.so.0 pkg/usr/lib/libcurl.so.4.1.1

You can see the needed files and should be able to find out which file belongs to which package.

==== license ====

The '''license''' tag must reflect the license of the source code. Please check the source tarball for COPYING, LICENSE, or other files with names that indicates that it contains licensing information. Beside the license file most developer include headers in the source code files with licensing details.

If the license is on the [https://spdx.org/licenses/ SPDX License List], use the identifier specified by SPDX.

If a package has a special/custom license we need to provide it with the release. Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows:

subpackages="$pkgname-doc"

Add a similar line to the following to your package() function, depending on the license description file:

install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING

If you follow these steps then abuild will automatically add the license to the package-doc apk for you.

{{Warning|It is not acceptable to package software with "unknown" license! If you can't find license of the source code, please contact the author and ask him to specify the license. }}

==== arch ====

The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (ie, a pure-python package).
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}

==== url ====

Website address for the program. This is usefully later on when either finding documentation or other information about the package.

==== pkgdesc ====

A brief, one line, description of what the package does. Useful for the package management system. It should start with a capital letter and does '''not''' end with a period.

Here is an example from apk_info for the OpenSSH client package:

pkgdesc="Port of OpenBSD's free SSH release - client"

==== pkgver ====

Provide the release number of the package you are building.

==== pkgrel ====

The $pkgrel versioning is made so if you change something to your APKBUILD file without changing the actual $pkgver you can increment pkgrel so apk tools will detect it as an update. For instance if you forget to add a dependency you can add it afterward and you can +1 pkgver so apk finds this update and add the missing dependency. When there's an upstream version changes, we reset the pkgrel to 0.

==== pkgname ====

The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"

==== install ====

There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:

<dl>
<dt>$pkgname.pre-install
<dd>This script is executed before package is installed. Typical use is when package needs a group and a user to be created. For example:
<pre>
#!/bin/sh

addgroup -S clamav 2>/dev/null
adduser -S -D -H -s /bin/false -G clamav -g clamav clamav 2>/dev/null

exit 0
</pre>
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and <code>apk add</code> will exit with failure.

<dt>$pkgname.post-install
<dd>This script is executed after package is installed. Can be used to generate font cache and similar.

<dt>$pkgname.pre-upgrade
<dd>Same as pre-install but is executed before upgrading/downgrading/reinstalling an already installed package. Note that exiting with failure will not cause apk to exit with failure, but will mark the package as broken.

<dt>$pkgname.post-upgrade
<dd>Same as post-install but is executed after upgrading/downgrading/reinstalling an already installed package.

<dt>$pkgname.pre-deinstall
<dd>This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.

<dt>$pkgname.post-deinstall
<dd>This script is executed after a package have been uninstalled. Can be used to update font caches and restore busybox links. For example:
<pre>
#!/bin/sh
busybox --install -s
</pre>

</dl>

If the package have an pre-install and post-install script the APKBUILD should have the ''install'' variable defined:
<pre>
...
install="$pkgname.pre-install $pkgname.post-install"

...
</pre>

==== subpackages ====

$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc.

The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system.

To see if you need the -dev package you can run the following cmd:

{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}

If this returns any files you need to include the -dev package.

 To see if you need the -doc package you can run the following cmd:

{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}

If this returns any directories you need to include the -doc package.

===== Custom subpackages =====

Some software additionally has non-essential files that do not qualify as either documentation or development content. These files should be placed in their own, specialized subpackage(s). Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function:

test() {
mkdir -p "$subpkgdir"/usr
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/
}

We also need to add the package info to $subpackages variable:

subpackages="$pkgname-doc $pkgname-dev $pkgname-test"

After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir.

The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add:

depends="perl"
makedepends="perl-dev"

If we would install the base package it would not install perl, but if we install the package-test package it would.

==== Patches ====

Please make sure you always submit human readable patches. Way's to create them are:

directory compare:

{{Cmd|diff -urp original_directory new_directory > filename.patch}}

file compare:

{{Cmd|diff -up original.file new.file > filename.patch}}

Because multiple patches can patch the same file, we could create offset for the next patch. To make sure we always patch in a specified way we should number the patches as followed:

10-patch1.patch 20-patch2.patch 30-patch3.patch

This way we are always sure patch 1 is first and if we want to add additional patches between them we can use 11,12,21,22...

Add names of the patch files to the ''source'' variable. If you haven't declared custom ''prepare'' function, then it's all what you need to do. Otherwise call ''default_prepare'' in your ''prepare'' function, for example:

prepare() {
default_prepare

# do your stuff
}

Note: Some older packages contain for loop in the ''prepare'' function to apply patches. This is not needed anymore, patches are handled by ''default_prepare''.

==== Configure options ====

Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location.

We are not covering the depend switches here we have discussed this already in the depend section.

==== Make options ====

If you notice weird problems when compiling or installing the package with make/make install you could try to disable [http://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be:

make

To disable parallel we use:

make -j1

We can use the same for make install.

Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed:

make DESTDIR="$pkgdir" install

Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and sudo when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.

==== builddir ====
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.

builddir="$srcdir"/$pkgname-$pkgver

==== Additional files ====

If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file):

install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf

== Build the package ==

If you did not already create the checksums as mentioned above you can do so now:

{{Cmd|cd $pkgname
abuild checksum}}

It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependency's from your repository and builds it, afterwards it will uninstall all those depending packages again. You could also use the '''-R''' switch which would build your package including the dependency packages.

{{Cmd|abuild -r}}

== Commit your work ==

After you successfully build your package you can submit your APKBUILD to Alpine's git repository.

Update your git repo, before adding new files:

{{Cmd|cd $aportsdir
git pull}}

This should pull all the changes made by others into you local git repo.

When you think you are ready you can add your files to git:

NOTE: when using our github repo, you can create PR's for each package. Please squash all commits into a single one per PR.

{{Cmd|cd $aportsdir
git add testing/$pkgdir (include any other files needed for the build; $pkgname.install...)
git commit}}

In the commit message, add the following (remove the comments in the last four lines):

{{Cmd| # Please enter the commit message for your changes
#[snip]
#
testing/$pkgname: new aport # this will be the subject line
# a blank line
$pkgurl # homepage of project
$pkgdesc # a one line description}}

Or you could add the following to your `aports/.git/hooks/prepare-commit-msg` to automatically generate the commit message:

#!/bin/sh
case "$2,$3" in
,|template,)
if git status --porcelain | grep -q '^A.*APKBUILD$'; then
meta() { git diff --staged | grep "^+$1" | sed 's/.*="\?//;s/"$//';}
cat > "$1" <<EOF
testing/$(meta pkgname): new aport

$(meta url)
$(meta pkgdesc)
EOF
else
git status --porcelain | sed -n 's/...$.*$\/APKBUILD/\1: /p;T;q' > "$1"
fi;;
esac

Now your changes are only available locally in your repository.

Because you do not have push rights to the Alpine aports repository you need to create a pull request to [https://github.com/alpinelinux/aports/ Alpine's mirror on GitHub] (read instructions [https://github.com/alpinelinux/aports/blob/master/.github/CONTRIBUTING.md here]).

Alternatively you can also create a diff (patch) of the changes you made and send this patch to the
[http://lists.alpinelinux.org/alpine-aports/ alpine-aports mailinglist].

To create a diff patch:

{{Cmd|git format-patch HEAD^}}

or if you have sprunge, you can create a link to your patch for convenience

{{Cmd|git format-patch HEAD^ --stdout <nowiki>|</nowiki> sprunge}}

== Send a patch ==

[[Creating_patches#Only_the_last_commit_with_.27git_send-email.27|git send-email]] will do that for you.

== See Also ==
* [[APKBUILD Reference]]
* [[APKBUILD examples]]
* [[Development using git]]
* [[Development using git:Quality assurance]]

[[Category:Development]]

Create UEFI boot USB

2017-12-12T15:37:01Z

OxR463: /* Copy gummiboot efi binary */

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Copy gummiboot efi binary ==

{{note| Gummiboot has been forked in Alpine Linux since it has been [https://www.freedesktop.org/wiki/Software/systemd/systemd-boot/ consumed by systemd upstream].}}

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We copy {{Path|gummibootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add gummiboot }}
{{Cmd | cp /usr/lib/gummiboot/gummibootx64.efi /mnt/EFI/Boot/bootx64.efi }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

Talk:Create UEFI boot USB

2017-12-12T15:31:46Z

OxR463:

<del>Ideally, gummiboot [systemd-boot] should be replaced by grub2 now that it has been consumed by systemd.
--[[User:OxR463|OxR463]] 19:52, 2 June 2017 (UTC)</del>

Hopefully I'm putting this in the correct spot, but I for one would also like to see instructions on configuring a UEFI bootable USB assuming there's already a boot manager such as rEFInd on the target system.[[User:Siernan|Regards, Siernan]] ([[User talk:Siernan|talk]]) 23:13, 14 August 2017 (UTC)

Talk:Developer Documentation

2017-11-29T17:08:53Z

OxR463:

I wonder if we should move/rename the "Alpine 'edge' buildsystem" out. In old days we had a separate build environment, a gentoo environment. We dont have that anymore. We just build in alpine so setting up build env is a question of ''apk add alpine-sdk'' and thats it.

Installing alpine in a chroot is other topic and not related to build env really.
--[[User:Ncopa|Ncopa]] 03:09, 21 May 2010 (UTC)

There does not seem to be any documentation concerning package stabilization procedures.
--[[User:OxR463|OxR463]] 17:08, 29 November 2017 (UTC)

User:OxR463

2017-11-01T15:24:08Z

OxR463: /* External */

<elitist>the command line is all you need anyway</elitist>

== External ==
* [https://github.com/lramage94/aports Aports Development Fork]
* [https://github.com/lramage94/overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://github.com/lramage94 Github]
* [https://wiki.postmarketos.org/wiki/User:Oxr463 PostmarketOS Wiki]
* [http://lramage94.github.io Website]

User:OxR463

2017-11-01T15:19:52Z

OxR463: /* External */

Create UEFI boot USB

2017-10-03T19:20:53Z

OxR463: Undo revision 14016 by OxR463 (talk)

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Copy gummiboot efi binary ==

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We copy {{Path|gummibootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add gummiboot }}
{{Cmd | cp /usr/lib/gummiboot/gummibootx64.efi /mnt/EFI/Boot/bootx64.efi }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

Create UEFI boot USB

2017-10-03T19:20:40Z

OxR463: Undo revision 14017 by OxR463 (talk)

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Create efi binary ==

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We copy {{Path|bootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add grub-efi }}
{{Cmd | grub-install --target=x86_64-efi --efi-directory=/mnt/EFI/Boot/ }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

Create UEFI boot USB

2017-10-03T19:20:28Z

OxR463: Undo revision 14018 by OxR463 (talk)

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Create efi binary ==

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We copy {{Path|bootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add grub-efi }}
{{Cmd | grub-install --target{{=}}x86_64-efi --efi-directory{{=}}/mnt/EFI/Boot/ }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

Create UEFI boot USB

2017-10-03T19:17:56Z

OxR463: /* Create efi binary */

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Create efi binary ==

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We install {{Path|bootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add grub-efi }}
{{Cmd | grub-install --target{{=}}x86_64-efi --efi-directory{{=}}/mnt/EFI/Boot/ }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

Create UEFI boot USB

2017-10-03T19:17:34Z

OxR463: /* Create efi binary */

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Create efi binary ==

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We copy {{Path|bootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add grub-efi }}
{{Cmd | grub-install --target{{=}}x86_64-efi --efi-directory{{=}}/mnt/EFI/Boot/ }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

Create UEFI boot USB

2017-10-03T19:13:53Z

OxR463: Replace gummiboot instructions with grub 2

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| this will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device}}

{{Cmd | parted --script /dev/sdX mklabel gpt}}
{{Cmd | parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 512MiB }}
{{Cmd | parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n Alpine /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt }}
{{Cmd | cd /mnt && uniso < /path/to/alpine-3.4.0-x86_64.iso }}

== Create efi binary ==

UEFI will look for a {{Path|EFI/bootx64.efi}} as a fallback efi loader. We copy {{Path|bootx64.efi}} to this location.

{{Cmd | mkdir -p /mnt/EFI/Boot }}
{{Cmd | apk add grub-efi }}
{{Cmd | grub-install --target=x86_64-efi --efi-directory=/mnt/EFI/Boot/ }}

== Create configuration files for boot loader ==

We need create some configuration files for gummiboot.
{{Cmd | mkdir -p loader/entries }}

{{Cat | loader/loader.conf |default alpine
timeout 4
}}

The options are taken from {{Path|boot/syslinux/syslinux.cfg}}

{{Cat | loader/entries/alpine.conf |title Alpine Linux
linux /boot/vmlinuz-hardened
initrd /boot/initramfs-hardened
options modloop{{=}}/boot/modloop-hardened modules{{=}}loop,squashfs,sd-mod,usb-storage quiet
}}

Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

User:OxR463

2017-10-03T18:50:20Z

OxR463: /* Rage */

<elitist>the command line is all you need anyway</elitist>

== External ==
* [https://github.com/lramage94/aports Aports Development Fork]
* [https://github.com/lramage94/gentoo-overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://github.com/lramage94 Github]
* [http://lramage94.github.io Website]

User:OxR463

2017-10-03T18:45:59Z

OxR463: Created page with "= Rage <OxR463> = <elitist>the command line is all you need anyway</elitist> == External == * [https://github.com/lramage94/aports Aports Development Fork] * [https://github..."

= Rage <OxR463> =

<elitist>the command line is all you need anyway</elitist>

== External ==
* [https://github.com/lramage94/aports Aports Development Fork]
* [https://github.com/lramage94/gentoo-overlay Ebuild Overlay]
* [http://wiki.gentoo.org/wiki/User:Rage/ Gentoo Wiki]
* [http://github.com/lramage94 Github]
* [http://lramage94.github.io Website]

Creating an Alpine package

2017-10-03T18:41:31Z

OxR463: Removed dead link to www.gentoo-portage.com; updated link to gentoo source tree

== Requirements ==

To build a package for Alpine Linux you need an Alpine Linux installation. Check the [[Installation]] page to see all available installation options.

== Setup your system and account ==
{{:Include:Setup_your_system_and_account_for_building_packages}}

== Getting some help ==

It might be wise to start by checking what the [[Abuild|abuild]] program can/cannot do.

{{Cmd|abuild -h}}

== Creating an APKBUILD file ==

=== Use a template APKBUILD ===

To create the actual APKBUILD file {{Pkg|newapkbuild}} can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.

If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.

{{:Include:Newapkbuild}}

{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}

[[Abuild_and_Helpers#apkbuild-cpan|apkbuild-cpan]] simplifies the creation of perl packages from CPAN and [[Abuild_and_Helpers#apkbuild-pypi|apkbuild-pypi]] ease the generation of APKBUILD files for python packages from PyPi.

If you are create a daemon package which needs initd scripts you can add the -c making it:

{{Cmd|newapkbuild -c ''packagename''}}

This will copy the sample initd and confd files to the build directory. 
A third file sample.install file will be copied as well (we will discuss this later on).

=== Modify your APKBUILD ===
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source).

If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like:

"$pkgdir"/somedir

This will prevent issues with spaces/special characters in the future.

{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}

=== APKBUILD variables/functions ===

==== source ====

The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.

Here are few things to note:

* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:
: {{cmd|abuild checksum}}
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}

* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre>
: (or similar depending on the package).

* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:
: <pre>http://oss.example.org/?get=software&ver=1.0</pre>
: You must prepend '${pkgname}-${pkgver}.tar.gz::' to the protocol, like so:
: <pre>source="${pkgname}-${pkgver}.tar.gz::http://oss.example.org/?get=software&ver=1.0"</pre>
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.

* Some projects didn't provide a release tarball. Beware that some git services (gitweg, cgit, …?) doesn’t provide ''stable'' tarballs, so when you point source to an tarball like <tt>http://repo.or.cz/w/gitstats.git/snapshot/ad7efbb9399e60cee6cb217c6b47e604174a8093.tar.gz</tt>, then you will run into issues because the checksum changes when downloading on the build system. This is not a problem on GitHub, GitLab and other decent services provides, they provide ''stable'' tarballs.

* abuild currently supports the following protocols for remote file retrieval:
** http
** https
** ftp



* abuild currently supports the following archive types/archive file extensions:
** .tar.gz / .tgz
** .tar.bz2
** .tar.lzma
** .tar.xz
** .zip

==== depends & makedepends ====

Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package, in depends you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [http://en.wikipedia.org/wiki/Rtfm RTFM].

No kidding, lots of important information can be found it the package INSTALL and README file (or the likes). Another good way is the run <code>./configure --help</code> from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a source directory you can create one with the command:

{{Cmd|abuild unpack}}

Running <code>configure</code> will also show you how you can disable a specific option for this package. A good example is for instance "--disable-nls" which will disable native language support and thus does not depend on gettext (libiconv, glib, ...).

Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided the package builder but please try to follow Alpine's design concept as much as possible.

An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo Linux ebuilds (previous versions of Alpine were based on Gentoo).

* [https://gitweb.gentoo.org/repo/gentoo.git/tree/ Gentoo Ebuilds]
* [http://www.archlinux.org/packages/search/ Arch Linux packages] [https://aur.archlinux.org/ Arch Linux User Repository]

After the package is successfully compiled and created we should make sure it didn't link to any package that is not present in the <code>$depends</code> variable. We do this by using <code>scanelf</code>. If scanelf is not yet installed on your system you can do that by installing {{Pkg|pax-utils}}.

{{Cmd|scanelf -nR pkg}}

An example output of {{Pkg|libcurl}} would be:

ET_DYN libssl.so.0.9.8,libcrypto.so.0.9.8,libz.so.1,libc.so.0,ld-uClibc.so.0 pkg/usr/lib/libcurl.so.4.1.1

You can see the needed files and should be able to find out which file belongs to which package.

==== license ====

The '''license''' tag must reflect the license of the source code. Please check the source tarball for COPYING, LICENSE, or other files with names that indicates that it contains licensing information. Beside the license file most developer include headers in the source code files with licensing details. Please use the short name and the release number in the license tag, e.g

{| cellpadding="5" border="1" class="wikitable"
|-
! Short name
! Full name
|-
| GPL2
| GNU General Public License Version 2.0
|-
| LGPL2+
| GNU Lesser General Public License Version 2.1
|-
| ASL 2.0
| Apache License Version 2.0
|-
| BSD
| BSD License
|-
| MIT
| MIT license
|-
| MPL 2.0
| Mozilla Public License v2.0
|-
| ZPL 2.0
| Zope Public License v 2.0
|-
| PHP
| PHP License v3.0
|-
| zlib
| zlib/libpng License
|-
|}

For the GNU General Public License the '+' means ''or (at your option) any later version.'' which covers future releases of that license. We skip the ''v'' because it's obvious that the number shows the version. If you are unsure about the short name of a license, please check the resources below for additional information.

* [https://wiki.archlinux.org/index.php/Licenses ArchLinux and Licensing]
* [https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Good_Licenses Fedora and Licensing]

If a package has a special/custom license we need to provide it with the release. Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows:

subpackages="$pkgname-doc"

Add a similar line to the following to your package() function, depending on the license description file:

install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING

If you follow these steps then abuild will automatically add the license to the package-doc apk for you.

==== arch ====

The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (ie, a pure-python package).
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}

==== url ====

Website address for the program. This is usefully later on when either finding documentation or other information about the package.

==== pkgdesc ====

A brief, one line, description of what the package does. Useful for the package management system. It should start with a capital letter and does '''not''' end with a period.

Here is an example from apk_info for the OpenSSH client package:

pkgdesc="Port of OpenBSD's free SSH release - client"

==== pkgver ====

Provide the release number of the package you are building.

==== pkgrel ====

The $pkgrel versioning is made so if you change something to your APKBUILD file without changing the actual $pkgver you can higer pkgrel so apk tools will detect it as an update. For instance if you forget to add a dependency you can add it afterward and you can +1 pkgver so apk finds this update and add the missing dependency. When there's an upstream version changes, we reset the pkgrel to 0.

==== pkgname ====

The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"

==== install ====

There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:

<dl>
<dt>$pkgname.pre-install
<dd>This script is executed before package is installed. Typical use is when package needs a group and a user to be created. For example:
<pre>
#!/bin/sh

addgroup -S clamav 2>/dev/null
adduser -S -D -H -s /bin/false -G clamav -g clamav clamav 2>/dev/null

exit 0
</pre>
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and <code>apk add</code> will exit with failure.

<dt>$pkgname.post-install
<dd>This script is executed after package is installed. Can be used to generate font cache and similar.

<dt>$pkgname.pre-upgrade
<dd>Same as pre-install but is executed before upgrading/downgrading/reinstalling an already installed package. Note that exiting with failure will not cause apk to exit with failure, but will mark the package as broken.

<dt>$pkgname.post-upgrade
<dd>Same as post-install but is executed after upgrading/downgrading/reinstalling an already installed package.

<dt>$pkgname.pre-deinstall
<dd>This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.

<dt>$pkgname.post-deinstall
<dd>This script is executed after a package have been uninstalled. Can be used to update font caches and restore busybox links. For example:
<pre>
#!/bin/sh
busybox --install -s
</pre>

</dl>

If the package have an pre-install and post-install script the APKBUILD should have the ''install'' variable defined:
<pre>
...
install="$pkgname.pre-install $pkgname.post-install"

...
</pre>

==== subpackages ====

$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc.

The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system.

To see if you need the -dev package you can run the following cmd:

{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}

If this returns any files you need to include the -dev package.

 To see if you need the -doc package you can run the following cmd:

{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}

If this returns any directories you need to include the -doc package.

===== Custom subpackages =====

Some software additionally has non-essential files that do not qualify as either documentation or development content. These files should be placed in their own, specialized subpackage(s). Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function:

test() {
mkdir -p "$subpkgdir"/usr
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/
}

We also need to add the package info to $subpackages variable:

subpackages="$pkgname-doc $pkgname-dev $pkgname-test"

After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir.

The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add:

depends="perl"
makedepends="perl-dev"

If we would install the base package it would not install perl, but if we install the package-test package it would.

==== Patches ====

Please make sure you always submit human readable patches. Way's to create them are:

directory compare:

{{Cmd|diff -urp original_directory new_directory > filename.patch}}

file compare:

{{Cmd|diff -up original.file new.file > filename.patch}}

Because multiple patches can patch the same file, we could create offset for the next patch. To make sure we always patch in a specified way we should number the patches as followed:

10-patch1.patch 20-patch2.patch 30-patch3.patch

This way we are always sure patch 1 is first and if we want to add additional patches between them we can use 11,12,21,22...

Add names of the patch files to the ''source'' variable. If you haven't declared custom ''prepare'' function, then it's all what you need to do. Otherwise call ''default_prepare'' in your ''prepare'' function, for example:

prepare() {
default_prepare

# do your stuff
}

Note: Some older packages contain for loop in the ''prepare'' function to apply patches. This is not needed anymore, patches are handled by ''default_prepare''.

==== Configure options ====

Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location.

We are not covering the depend switches here we have discussed this already in the depend section.

==== Make options ====

If you notice weird problems when compiling or installing the package with make/make install you could try to disable [http://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be:

make

To disable parallel we use:

make -j1

We can use the same for make install.

Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed:

make DESTDIR="$pkgdir" install

Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and sudo when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.

==== builddir ====
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.

builddir="$srcdir"/$pkgname-$pkgver

==== Additional files ====

If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file):

install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf

== Build the package ==

If you did not already create the checksums as mentioned above you can do so now:

{{Cmd|cd $pkgname
abuild checksum}}

It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependency's from your repository and builds it, afterwards it will uninstall all those depending packages again. You could also use the '''-R''' switch which would build your package including the dependency packages.

{{Cmd|abuild -r}}

== Commit your work ==

After you successfully build your package you can submit your APKBUILD to Alpine's git repository.

Update your git repo, before adding new files:

{{Cmd|cd $aportsdir
git pull}}

This should pull all the changes made by others into you local git repo.

When you think you are ready you can add your files to git:

NOTE: when using our github repo, you can create PR's for each package. Please squash all commits into a single one per PR.

{{Cmd|cd $aportsdir
git add testing/$pkgdir (include any other files needed for the build; $pkgname.install...)
git commit}}

In the commit message, add the following (remove the comments in the last four lines):

{{Cmd| # Please enter the commit message for your changes
#[snip]
#
testing/$pkgname: new aport # this will be the subject line
# a blank line
$pkgurl # homepage of project
$pkgdesc # a one line description}}

Or you could add the following to your `aports/.git/hooks/prepare-commit-msg` to automatically generate the commit message:

#!/bin/sh
case "$2,$3" in
,|template,)
if git status --porcelain | grep -q '^A.*APKBUILD$'; then
meta() { git diff --staged | grep "^+$1" | sed 's/.*="\?//;s/"$//';}
cat > "$1" <<EOF
testing/$(meta pkgname): new aport

$(meta url)
$(meta pkgdesc)
EOF
else
git status --porcelain | sed -n 's/...$.*$\/APKBUILD/\1: /p;T;q' > "$1"
fi;;
esac

Now your changes are only available locally in your repository.

Because you do not have push rights to the Alpine aports repository you need to create a pull request to [https://github.com/alpinelinux/aports/ Alpine's mirror on GitHub] (read instructions [https://github.com/alpinelinux/aports/blob/master/.github/CONTRIBUTING.md here]).

Alternatively you can also create a diff (patch) of the changes you made and send this patch to the
[http://lists.alpinelinux.org/alpine-aports/ alpine-aports mailinglist].

To create a diff patch:

{{Cmd|git format-patch HEAD^}}

or if you have sprunge, you can create a link to your patch for convenience

{{Cmd|git format-patch HEAD^ --stdout <nowiki>|</nowiki> sprunge}}

== Send a patch ==

[[Creating_patches#Only_the_last_commit_with_.27git_send-email.27|git send-email]] will do that for you.

== See Also ==
* [[APKBUILD Reference]]
* [[APKBUILD examples]]
* [[Development using git]]
* [[Development using git:Quality assurance]]

[[Category:Development]]

Talk:Create UEFI boot USB

2017-06-02T19:52:33Z

OxR463: Created page with "Ideally, gummiboot [systemd-boot] should be replaced by grub2 now that it has been consumed by systemd. --OxR463 19:52, 2 June 2017 (UTC)"

Ideally, gummiboot [systemd-boot] should be replaced by grub2 now that it has been consumed by systemd.
--[[User:OxR463|OxR463]] 19:52, 2 June 2017 (UTC)