Alpine Linux - User contributions [en]

NVIDIA

2023-02-15T17:03:40Z

User4708: /* Nouveau */

== Nouveau ==
'''Nouveau''' is a open-source driver for NVIDIA GPUs.

=== Wayland ===

Install the following packages as needed:

* <code>mesa-dri-gallium</code>: '''necessary''' Mesa drivers.
* <code>mesa-va-gallium</code>: VA-API drivers, for hardware accelerated video encoding and decoding

If driver auto-selection does not work, e.g. no mouse cursor under Sway, manual driver selection might be needed:

* <code>export MESA_LOADER_DRIVER_OVERRIDE=nouveau</code>

For VA-API:
* <code>export LIBVA_DRIVER_NAME=nouveau</code>

== Proprietary Driver ==

As of Decemeber 2022 the proprietary NVIDIA driver does not support the [https://musl.libc.org/ musl libc].

[[Category:Drivers]]

Flatpak

2023-01-03T05:54:40Z

User4708:

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snap_(software) Snap],

= Setup / Installation =

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add flatpak}}

It's recommended to run flatpak as your user, rather than as root. Therefore, add your user to the flatpak group:

{{cmd|# adduser <YourUsername> flatpak}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

 

= Usage =

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

 

==== Search ====

To search for applications run '''flatpak search <appplicationname>'''

Example:
{{cat|flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

==== Install ====

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

 

==== Remove ====

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

 

= Developers =

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

= Troubleshooting =

==== Permission errors ====

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group, See step two of [[Flatpak#Setup_/_Installation|Setup / Installation]].

{{Note|You may need to log out and log back in or reboot for the group change(s) to take effect}}

 

==== Fixing audio issues ====

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in /etc/profile.d/xdg_runtime_dir.sh and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:
{{Cmd|pulseaudio --start && flatpak run com.example.Example}}

 

= Links =
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

 

= See Also =

[[Category:Package Manager]]
[[Category: Desktop]]

KDE

2022-12-21T06:33:35Z

User4708:

[[File:KDEScreenshot.png |thumb |KDE Plasma screenshot.]]

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

{{Note|the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. However, the rest of Plasma can be installed separately to get a functional desktop.}}

 

== Prerequisites ==

* [[Installation|Install]] AlpineLinux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Managing_repositories|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]

{{Note|[[Wayland]] can be used but may be less stable and Plasma may still require Xorg}}

 

== Installation ==

==== Standard plasma installation ====

{{Cmd|# apk add plasma elogind polkit-elogind dbus}}

This will install the required Plasma packages, {{Pkg|sddm}} and pre-configure it to use the Breeze theme.

 

==== Lightweight plasma installation ====

Alternatively, a smaller installation can be done:

{{Cmd|# apk add plasma-desktop systemsettings sddm breeze elogind polkit-elogind dbus}}

{{Note|If you are missing something that is in a standard Plasma installation check out the dependencies of the {{Pkg|plasma}} package because it is likely you will find whatever your missing there.}}

 

For both installation methods you need to enable the following services:

{{Cmd|# rc-update add dbus}}
{{Cmd|# rc-update add elogind}}
{{Cmd|# rc-update add polkit}}
{{Cmd|# rc-update add udev}}

 

{{Note|'''polkit''' and '''udev''' are technically optional (or have other alternatives) but if they are not installed/started features (or the system) may not work properly, modify this at your own risk!}}

 

== KDE Applications ==

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a smaller set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

 

== Starting Plasma ==

Plasma can be started using a display manager or from the console.

==== Using a display manager ====

When Plasma is installed via the {{Pkg|plasma}} meta-package, the display manager is set up using {{Pkg|sddm}}.

Make sure you enable and start the SDDM service.

<pre>
rc-update add sddm
rc-service sddm start
</pre>

* Select ''Plasma'' to launch a new session in Wayland
* Select ''Plasma (X11)'' to launch a new session in Xorg

==== From the console ====

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. To start X:
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

 

== See also ==
* [[Installation#Post-Installation|Post installation]]
* [[Flatpak]]

[[Category:Desktop]]

NVIDIA

2022-12-21T06:27:45Z

User4708: Added the drivers category and added info to the Proprietary Drivers section.

== Nouveau ==
'''Nouveau''' is the open-source driver for NVIDIA GPUs.

=== Wayland ===

Install the following packages as needed:

* <code>mesa-dri-gallium</code>: '''necessary''' Mesa drivers.
* <code>mesa-va-gallium</code>: VA-API drivers, for hardware accelerated video encoding and decoding

If driver auto-selection does not work, e.g. no mouse cursor under Sway, manual driver selection might be needed:

* <code>export MESA_LOADER_DRIVER_OVERRIDE=nouveau</code>

For VA-API:
* <code>export LIBVA_DRIVER_NAME=nouveau</code>

== Proprietary Driver ==

As of Decemeber 2022 the proprietary NVIDIA driver does not support the [https://musl.libc.org/ musl libc].

[[Category:Drivers]]

Nvidia Video

2022-12-21T06:12:52Z

User4708: User4708 moved page Nvidia Video to NVIDIA: NVIDIA is more inline with other Linux distro docs - NVIDIA is spelled in captial letters on the NVIDA website

#REDIRECT [[NVIDIA]]

NVIDIA

2022-12-21T06:12:52Z

User4708: User4708 moved page Nvidia Video to NVIDIA: NVIDIA is more inline with other Linux distro docs - NVIDIA is spelled in captial letters on the NVIDA website

KDE

2022-12-13T18:24:04Z

User4708: Changed link to reflect changes made to the Repositories page.

[[File:KDEScreenshot.png |thumb |KDE Plasma screenshot.]]

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

{{Note|the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. However, the rest of Plasma can be installed separately to get a functional desktop.}}

 

== Prerequisites ==

* [[Installation|Install]] AlpineLinux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Managing_repositories|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]

{{Note|[[Wayland]] can be used but may be less stable and Plasma may still require Xorg}}

 

== Installation ==

==== Standard plasma installation ====

{{Cmd|# apk add plasma elogind polkit-elogind dbus}}

This will install the required Plasma packages, {{Pkg|sddm}} and pre-configure it to use the Breeze theme.

 

==== Lightweight plasma installation ====

Alternatively, a smaller installation can be done:

{{Cmd|# apk add plasma-desktop systemsettings sddm breeze elogind polkit-elogind dbus}}

 

{{Note|If you are missing something that is in a standard Plasma installation check out the dependencies of the {{Pkg|plasma}} package because it is likely you will find whatever your missing there.}}

 

For both installation methods you need to enable the following services:

{{Cmd|# rc-update add dbus}}
{{Cmd|# rc-update add elogind}}
{{Cmd|# rc-update add polkit}}
{{Cmd|# rc-update add udev}}

 

{{Note|'''polkit''' and '''udev''' are technically optional (or have other alternatives) but if they are not installed/started features (or the system) may not work properly, modify this at your own risk!}}

 

== KDE Applications ==

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a smaller set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

 

== Starting Plasma ==

Plasma can be started using a display manager or from the console.

==== Using a display manager ====

When Plasma is installed via the {{Pkg|plasma}} meta-package, the display manager is set up using {{Pkg|sddm}}.

Make sure you enable and start the SDDM service.

<pre>
rc-update add sddm
rc-service sddm start
</pre>

* Select ''Plasma'' to launch a new session in Wayland
* Select ''Plasma (X11)'' to launch a new session in Xorg

==== From the console ====

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. To start X:
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

 

== See also ==
* [[Installation#Post-Installation|Post installation]]
* [[Flatpak]]

[[Category:Desktop]]

Flatpak

2022-12-13T18:22:25Z

User4708: /* Troubleshooting */

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snappy_(package_manager) Snap],

= Setup / Installation =

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add flatpak}}

It's recommended to run flatpak as your user, rather than as root. Therefore, add your user to the flatpak group:

{{cmd|# adduser <YourUsername> flatpak}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

 

= Usage =

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

 

==== Search ====

To search for applications run '''flatpak search <appplicationname>'''

Example:
{{cat|flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

==== Install ====

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

 

==== Remove ====

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

 

= Developers =

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

= Troubleshooting =

==== Permission errors ====

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group, See step two of [[Flatpak#Setup_/_Installation|Setup / Installation]].

{{Note|You may need to log out and log back in or reboot for the group change(s) to take effect}}

 

==== Fixing audio issues ====

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in /etc/profile.d/xdg_runtime_dir.sh and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:
{{Cmd|pulseaudio --start && flatpak run com.example.Example}}

 

= Links =
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

 

= See Also =

[[Category:Package Manager]]
[[Category: Desktop]]

Flatpak

2022-12-13T18:21:02Z

User4708: /* Setup / Installation */

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snappy_(package_manager) Snap],

= Setup / Installation =

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add flatpak}}

It's recommended to run flatpak as your user, rather than as root. Therefore, add your user to the flatpak group:

{{cmd|# adduser <YourUsername> flatpak}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

 

= Usage =

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

 

==== Search ====

To search for applications run '''flatpak search <appplicationname>'''

Example:
{{cat|flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

==== Install ====

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

 

==== Remove ====

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

 

= Developers =

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

= Troubleshooting =

==== Permission errors ====

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group, see step two of [[Flatpak#Setup_/_Installation|Setup / Installation]].

{{Note|You may need to log out and log back in or reboot for the group change(s) to take effect}}

 

==== Fixing audio issues ====

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in /etc/profile.d/xdg_runtime_dir.sh and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:
{{Cmd|pulseaudio --start && flatpak run com.example.Example}}

 

= Links =
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

 

= See Also =

[[Category:Package Manager]]
[[Category: Desktop]]

Flatpak

2022-12-13T18:20:07Z

User4708: Removed repeated "adduser <YourUsername> flatpak" and replaced it with a link back to step 2 of Setup / Installation which already covers this.

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snappy_(package_manager) Snap],

= Setup / Installation =

''From: https://flatpak.org/setup/Alpine/''

To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]

To install Flatpak run:

{{cmd|# apk add flatpak}}

It's recommended to run flatpak as your user, rather than as root. Therefore, add your user to the flatpak group:

{{cmd|# adduser <YourUsername> flatpak}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

 

= Usage =

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

 

==== Search ====

To search for applications run '''flatpak search <appplicationname>'''

Example:
{{cat|flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

==== Install ====

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

 

==== Remove ====

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

 

= Developers =

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

= Troubleshooting =

==== Permission errors ====

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group, see step two of [[Flatpak#Setup_/_Installation|Setup / Installation]].

{{Note|You may need to log out and log back in or reboot for the group change(s) to take effect}}

 

==== Fixing audio issues ====

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in /etc/profile.d/xdg_runtime_dir.sh and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:
{{Cmd|pulseaudio --start && flatpak run com.example.Example}}

 

= Links =
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

 

= See Also =

[[Category:Package Manager]]
[[Category: Desktop]]

KDE

2022-12-12T22:02:02Z

User4708: /* See also */ - Changed link

[[File:KDEScreenshot.png |thumb |KDE Plasma screenshot.]]

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

{{Note|the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. However, the rest of Plasma can be installed separately to get a functional desktop.}}

 

== Prerequisites ==

* [[Installation|Install]] AlpineLinux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Enabling_the_community_repository|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]

{{Note|[[Wayland]] can be used but may be less stable and Plasma may still require Xorg}}

 

== Installation ==

==== Standard plasma installation ====

{{Cmd|# apk add plasma elogind polkit-elogind dbus}}

This will install the required Plasma packages, {{Pkg|sddm}} and pre-configure it to use the Breeze theme.

 

==== Lightweight plasma installation ====

Alternatively, a smaller installation can be done:

{{Cmd|# apk add plasma-desktop systemsettings sddm breeze elogind polkit-elogind dbus}}

 

{{Note|If you are missing something that is in a standard Plasma installation check out the dependencies of the {{Pkg|plasma}} package because it is likely you will find whatever your missing there.}}

 

For both installation methods you need to enable the following services:

{{Cmd|# rc-update add dbus}}
{{Cmd|# rc-update add elogind}}
{{Cmd|# rc-update add polkit}}
{{Cmd|# rc-update add udev}}

 

{{Note|'''polkit''' and '''udev''' are technically optional (or have other alternatives) but if they are not installed/started features (or the system) may not work properly, modify this at your own risk!}}

 

== KDE Applications ==

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a smaller set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

 

== Starting Plasma ==

Plasma can be started using a display manager or from the console.

==== Using a display manager ====

When Plasma is installed via the {{Pkg|plasma}} meta-package, the display manager is set up using {{Pkg|sddm}}.

Make sure you enable and start the SDDM service.

<pre>
rc-update add sddm
rc-service sddm start
</pre>

* Select ''Plasma'' to launch a new session in Wayland
* Select ''Plasma (X11)'' to launch a new session in Xorg

==== From the console ====

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. To start X:
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

 

== See also ==
* [[Installation#Post-Installation|Post installation]]
* [[Flatpak]]

[[Category:Desktop]]

Apk spec

2022-12-12T21:55:11Z

User4708: Changed Package_managment to Alpine Package Keeper.

{{Draft}}

For end-user facing documentation about apk, check out the [[Alpine_Package_Keeper|Alpine Package Keeper]] page.

This page is an attempt to document the internal data structures of the apk package manager. The canonical implementation of the apk format is [https://gitlab.alpinelinux.org/alpine/apk-tools apk-tools] and much of this information is gleaned from reading the source code.

There are three generations of the APK data formats. Version 1 is deprecated and no longer used, version 2 is currently the main version in use by apk-tools, and version 3 is under development. This page mostly describes the data formats used in version 2.

= Background =
== Tar Segments ==
Tar segments are a set of tar records. Normal tar files contain two null records at the end of the tar file to signal the end of the tarball. Tar segments are lacking these two records and can thus be concatenated before other tar files and will behave as one continuous tar file. The APK v2 package format makes use of both tar segments and tarballs.

Tar segments can be compressed using gzip compression. Gzip is a stream-based file format and multiple streams can be concatenated together. Most tooling will treat multiple gzip streams within a file as if it were a single stream. APK v2 files are aware of gzip streams and use them for file segmentation.

= Package Format V2 =
== Binary Format ==
APK v2 packages contain two tar segments followed by a tarball each in their own gzip stream (3 streams total). These streams contain the package signature, control data, and package data. The package data is a tarball of the files contained in a package laid out in a way that allows it to be unpacked at the filesystem root such that all files are placed in the correct location on the system. The control tar segment contains the package metadata along with any install scripts. The signature tar segment contains a single file that is a binary signature over the concatenated control segment and data tarball.

The signature file is a DER encoded PKCS1v15 RSA signature of the SHA1 hash of the concatenated control and data gzip streams. The filename has the format <tt>.SIGN.RSA.<key_name>.rsa.pub</tt> (for example <tt>.SIGN.RSA.alpine-devel@lists.alpinelinux.org-5261cecb.rsa.pub</tt>). This file is placed inside of a tar record with permissions 0644, uid 0, and gid 0. This tar record (lacking end-of-tar records) is gzip compressed, forming a signature tar segment, and is concatenated onto the front of the combined control and data segments. [https://gitlab.alpinelinux.org/alpine/abuild/-/blob/master/abuild-sign.in abuild-sign] is responsible for generating these signature segments.

The control segment contains the package metadata in a <tt>.PKGINFO</tt> file as well as all of the scripts (if any) that are used by apk during installation and removal of the package. For historical reasons all files in the control tar segment are prefixed with a dot (<tt>.</tt>). The control segment is constructed by placing each file for the package into a tar record, concatenating those tar records, gzipping the tar records, and concatenating them onto the front of the data tarball. The SHA1 hash of this gzip stream is used as the checksum <tt>C:</tt> field in the APKINDEX file.

The data tarball is a standard gzipped tarball with extra PAX headers that contain the SHA1 hash of each file in the tar header for that file. The hash is contained in a header called <tt>APK-TOOLS.checksum.SHA1</tt>. Unlike the other tar streams this tarball does contain the two end-of-tar null records. It is always the final segment of an APK package. Hashes are added with the [https://gitlab.alpinelinux.org/alpine/abuild/-/blob/master/abuild-tar.c abuild-tar] tool.

== PKGINFO Format ==
The PKGINFO file contains the package metadata. This is a plain-text file similar to INI files. Lines that begin with <tt>#</tt> are comments and ignored. Unlike INI files the parsing format of this file is very strict. Each key-value pair must be separated by exactly one space, one equal sign, and one more space (<tt> = </tt>). Keys may be repeated in this file and should be treated as a list of values if repetitions are found.

The specification for what fields are valid in PKGINFO is largely defined by [https://gitlab.alpinelinux.org/alpine/abuild/-/blob/master/abuild.in abuild]. As of July 2022 the following fields are supported:

* <tt>pkgname</tt> - package name
* <tt>pkgver</tt> - package version
* <tt>pkgdesc</tt> - package description
* <tt>url</tt> - package url
* <tt>builddate</tt> - unix timestamp of the package build date/time
* <tt>packager</tt> - name (and typically email) of person who built the package
* <tt>size</tt> - the installed-size of the package
* <tt>arch</tt> - the architecture of the package (ex: x86_64)
* <tt>origin</tt> - the origin name of the package
* <tt>commit</tt> - the commit hash from which the package was built
* <tt>maintainer</tt> - name (and typically email) of the package maintainer
* <tt>replaces_priority</tt> - replaces priority field for package (integer)
* <tt>provider_priority</tt> - provider priority for the package (integer)
* <tt>license</tt> - license string for the package
* <tt>depend</tt> - dependencies for the package (repeated)
* <tt>replaces</tt> - packages this package replaces (repeated)
* <tt>provides</tt> - what this package provides (repeated)
* <tt>triggers</tt> - what packages this package triggers on (repeated)
* <tt>install_if</tt> - install this package if these packages are present (repeated)
* <tt>datahash</tt> - hex-encoded sha256 checksum of the data tarball

== Example of PKGINFO ==
<pre>
# Generated by abuild 3.9.0-r2
# using fakeroot version 1.25.3
# Wed Jul 6 19:09:49 UTC 2022
pkgname = busybox
pkgver = 1.35.0-r18
pkgdesc = Size optimized toolbox of many common UNIX utilities
url = https://busybox.net/
builddate = 1657134589
packager = Buildozer <alpine-devel@lists.alpinelinux.org>
size = 958464
arch = x86_64
origin = busybox
commit = 332d2fff53cd4537d415e15e55e8ceb6fe6eaedb
maintainer = Sören Tempel <soeren+alpine@soeren-tempel.net>
provider_priority = 100
license = GPL-2.0-only
replaces = busybox-initscripts
provides = /bin/sh
triggers = /bin /usr/bin /sbin /usr/sbin /lib/modules/*
# automatically detected:
provides = cmd:busybox=1.35.0-r18
provides = cmd:sh=1.35.0-r18
depend = so:libc.musl-x86_64.so.1
datahash = 7d3351ac6c3ebaf18182efb5390061f50d077ce5ade60a15909d91278f70ada7
</pre>

== Package Building Example ==
This is a set of commands to partially build a package. '''DO NOT DO THIS''', it's mainly an example to see how this all fits together. Use the official build tools to build packages.

<pre>
tar -c .PKGNIFO .pre-install | abuild-tar --cut | gzip -9 > $controldir/control.tar.gz
cd $pkgdir; tar -c * | abuild-tar --hash | gzip -9 > $controldir/data.tar.gz
cat $controldir/control.tar.gz $controldir/data.tar.gz > mypackage-1.0-r0.apk
</pre>

= Index Format V2 =
== Binary Format ==
The index is served as [http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz APKINDEX.tar.gz] and is downloaded by apk to power the package database. The index is signed similarly to packages. The main difference between the index and packages is that the index file contains only two segments.

The signature segment is identical to a package segment and is concatenated, in its own gzip stream, to the beginning of the APKINDEX tarball.

The APKINDEX tarball contains two files: a DESCRIPTION file and an APKINDEX file. Each of these files is in their own tar record and the final record is followed by the standard end-of-tar null records. The DESCRIPTION file is a simple text file containing a description of the index (ex: <tt>community v20210212-7170-g5c9853dc69</tt>). The APKINDEX file is a text file containing records for each package in the repository in a text-based format. Each record is separated by a newline.

== APKINDEX Format ==
The APKINDEX file contains a set of records extracted from the PKGINFO file of each package in the repository. Each line is prefixed with a letter, colon, and is followed by the value of the field. Lines are newline (<tt>\n</tt>) terminated and there is one blank line between records for a package.

The <tt>apk_pkg_write_index_entry</tt> function of [https://gitlab.alpinelinux.org/alpine/apk-tools/-/blob/ff7c8f6ee9dfa2add57b88dc271f6711030e72a0/src/package.c#L905 package.c] defines the currently accepted fields. As of July 2022, these are:

* <tt>C:</tt> - file checksum, see below
* <tt>P:</tt> - package name (corresponds to <tt>pkgname</tt> in PKGINFO)
* <tt>V:</tt> - package version (corresponds to <tt>pkgver</tt> in PKGINFO)
* <tt>A:</tt> - architecture (corresponds to <tt>arch</tt> in PKGINFO), optional
* <tt>S:</tt> - size of entire package, integer
* <tt>I:</tt> - installed size, integer (corresponds to <tt>size</tt> in PKGINFO)
* <tt>T:</tt> - description (corresponds to <tt>pkgdesc</tt> in PKGINFO)
* <tt>U:</tt> - url (corresponds to <tt>url</tt> in PKGINFO)
* <tt>L:</tt> - license (corresponds to <tt>license</tt> in PKGINFO)
* <tt>o:</tt> - origin (corresponds to <tt>origin</tt> in PKGINFO), optional
* <tt>m:</tt> - maintainer (corresponds to <tt>maintainer</tt> in PKGINFO), optional
* <tt>t:</tt> - build time (corresponds to <tt>builddate</tt> in PKGINFO), optional
* <tt>c:</tt> - commit (corresponds to <tt>commit</tt> in PKGINFO), optional
* <tt>k:</tt> - provider priority, integer (corresponds to <tt>provider_priority</tt> in PKGINFO), optional
* <tt>D:</tt> - dependencies (corresponds to <tt>depend</tt> in PKGINFO, concatenated by spaces into a single line)
* <tt>p:</tt> - provides (corresponds to <tt>provides</tt> in PKGINFO, concatenated by spaces into a single line)
* <tt>i:</tt> - install if (corresponds to <tt>install_if</tt> in PKGINFO, concatenated by spaces into a single line)

== Package Checksum Field ==
The package checksum field is the SHA1 hash of the second gzip stream (control stream) in the package. The binary hash digest is base64 encoded. This is prefixed with <tt>Q1</tt> to differentiate it from the MD5 hashes used in older index formats. It is not possible to compute this checksum with standard command line tools but the apk-tools can compute it in their <tt>index</tt> operation.

== Example APKINDEX Record ==
<pre>
C:Q1P4IRU/u5yB4CSnUEBRD1WWwajrY=
P:jool-tools
V:4.1.5-r0
A:x86_64
S:140605
I:434176
T:Userspace control tools for SIIT / NAT64 Jool
U:https://www.jool.mx
L:GPL-2.0-only
o:jool-tools
m:Jakub Jirutka <jakub@jirutka.cz>
t:1620480809
c:771b3b0910ea9c7736db6ca4ff5c37ca9cf9af0d
D:so:libc.musl-x86_64.so.1 so:libnl-3.so.200 so:libnl-genl-3.so.200
p:cmd:jool=4.1.5-r0 cmd:jool_siit=4.1.5-r0 cmd:joold=4.1.5-r0
</pre>

= Installed Database V2 =
The installed database is used by apk to track which packages are installed and what modifications those packages have made to the system. This file is located at <tt>/lib/apk/db/installed</tt>. The installed file is a plaintext file of the same format as APKINDEX (contained in APKINDEX.tar.gz). It is neither compressed nor signed. Each record in the installed file starts with a package index record with the same fields as the APKINDEX file. The installed file adds some additional fields that are defined in [https://gitlab.alpinelinux.org/alpine/apk-tools/-/blob/ff7c8f6ee9dfa2add57b88dc271f6711030e72a0/src/database.c#L937 database.c]. As of July 2022 these additional fields are:

* <tt>r:</tt> - packages which this package replaces, space separated list
* <tt>q:</tt> - replaces priority, integer, optional
* <tt>s:</tt> - repository tag, optional, this will be set if the package is tagged to a repository in the world file (ex: linux@testing)
* <tt>f:</tt> - indicates broken items, space separated (f=files, s=scripts, x=xattrs, S=file hashes)

The following fields are repeated and in groups consist of a set of mutations made to the system to install the package.

ACL lines are specified as uid, colon, gid, colon, and mode.

* <tt>F:</tt> - directory name that was created by package, repeated
* <tt>M:</tt> - directory ACL, only if different than the default of 0:0:0755
* <tt>R:</tt> - file name, relative to preceding directory name
* <tt>a:</tt> - file ACL
* <tt>Z:</tt> - file checksum, if the checksum in the package is not none, a <tt>Q1</tt> prefix indicates this will be a SHA1 hash in base64 format

[[Category:Package Manager]] [[Category:Development]]

Flatpak

2022-12-10T06:24:27Z

User4708:

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snappy_(package_manager) Snap],

= Setup / Installation =

''From: https://flatpak.org/setup/Alpine/''

To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]

To install Flatpak run:

{{cmd|# apk add flatpak}}

It's recommended to run flatpak as your user, rather than as root. Therefore, add your user to the flatpak group:

{{cmd|# adduser <YourUsername> flatpak}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

 

= Usage =

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

 

==== Search ====

To search for applications run '''flatpak search <appplicationname>'''

Example:
{{cat|flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

==== Install ====

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

 

==== Remove ====

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

 

= Developers =

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

= Troubleshooting =

==== Permission errors ====

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group:

{{cmd|adduser <YourUsername> flatpak}}

 

{{Note|You may need to log out and log back in or reboot for the group change(s) to take effect}}

 

==== Fixing audio issues ====

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in /etc/profile.d/xdg_runtime_dir.sh and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:
{{Cmd|pulseaudio --start && flatpak run com.example.Example}}

 

= Links =
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

 

= See Also =

[[Category:Package Manager]]
[[Category: Desktop]]

Flatpak

2022-12-09T21:34:10Z

User4708: Changed link to Repositories#Managing_repositories

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snappy_(package_manager) Snap],

= Setup / Installation =

''From: https://flatpak.org/setup/Alpine/''

To install Flatpak you will need to enable the Community repository, See: [https://wiki.alpinelinux.org/wiki/Repositories#Managing_repositories Repositories - Managing repositories]

To install Flatpak run:

{{cmd|# apk add flatpak}}

It's recommended to run flatpak as your user, rather than as root. Therefore, add your user to the flatpak group:

{{cmd|# adduser <YourUsername> flatpak}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

 

= Usage =

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

 

==== Search ====

To search for applications run '''flatpak search <appplicationname>'''

Example:
{{cat|flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

==== Install ====

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

 

==== Remove ====

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

 

= Developers =

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

= Troubleshooting =

==== Permission errors ====

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group:

{{cmd|adduser <YourUsername> flatpak}}

 

{{Note|You may need to log out and log back in or reboot for the group change(s) to take effect}}

 

==== Fixing audio issues ====

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in /etc/profile.d/xdg_runtime_dir.sh and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:
{{Cmd|pulseaudio --start && flatpak run com.example.Example}}

 

= Links =
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

 

= See Also =

[[Category:Package Manager]]
[[Category: Desktop]]

Repositories

2022-12-09T21:31:37Z

User4708: Removed sections for enabling the community/edge repositories that is covered in Managing repositories, Left Using the testing repositories on stable branches

{{TOC right}}

The Alpine software repositories have three branches:

* '''main''' packages are the software that have direct support and updates from the Alpine core and main team. They also have official special documentation, are always available for all releases and will have substitutions if some are not continued from upstream. Commonly these packages are selected due to their responsibility and stability with respect to upstream availability. Packages from ''community'' or (rarely) ''testing'', that are accepted go to the ''main'' branch.

* '''community''' packages are those made by users in team with the official developers and close to the Alpine package process. They are supported by those user(s) contributions and could end if the user(s) stops; they may also be removed in a future release due to lack of support by upstream authors. Packages from ''testing'' that are accepted go to the ''community'' branch.

* '''testing''' packages are where new packages go. These are made by any contributor to Alpine. Testing has no release linked. The ''testing'' repository is only available on ''edge''. Packages from ''testing'' that are accepted go to the ''community'' branch or (rarely) the ''main'' branch.

= Managing repositories =

To enable a repository, remove the '''#''' in front of the URL along with any blank space.

Example: Disabled
{{cat|/etc/apk/repositories|#http://dl-cdn.alpinelinux.org/alpine/v3.16/community}}

Example: Enabled
{{cat|/etc/apk/repositories|http://dl-cdn.alpinelinux.org/alpine/v3.16/community}}

To edit the repositories, open the <code>/etc/apk/repositories</code> file in a text editor:

{{cmd|# <editor> /etc/apk/repositories}}

The default will look something like:

{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.16/main
#http://dl-cdn.alpinelinux.org/alpine/v3.16/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

After making changes to <code>/etc/apk/repositories</code> you should update the package index using:
{{cmd|# apk update}}

=== Changing repositories to https ===
For better security you should probably change the url's from '''http''' to '''https'''. [https://en.wikipedia.org/wiki/HTTPS#Technical]

{{Note|Some Alpine Linux package mirrors may not support '''https'''. If that is the case, you will need to change mirrors or revert back. You can check if your mirror supports '''https''' on https://mirrors.alpinelinux.org }}

=== Avoid manually changing the repositories file for a new release ===

You can avoid having to manually update the version in <code>/etc/apk/repositories</code> for each Alpine Linux release by changing <code>v3.16</code> to <code>latest-stable</code>.

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
https://dl-cdn.alpinelinux.org/alpine/latest-stable/main
https://dl-cdn.alpinelinux.org/alpine/latest-stable/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Warning|Changing the repositories to <code>latest-stable</code> may initiate unexpected release upgrades.}}

= Release Branches =

There are several release branches for Alpine Linux available at the same time. Each May and November we make a release branch from '''edge'''. The '''main''' repository is typically supported for 2 years and the '''community''' repository is supported until next stable release.

Security fixes beyond that can be made on request when there are patches available.

== Main ==

By default only the '''main''' repository is enabled. ''main'' has a support cycle of 2 years. We also try to limit the amount of packages in ''main'' to only include base system packages, in base you can think of packages which are needed by other packages or are needed to setup a basic system. Packages in ''main'' must '''not''' have dependencies in other repositories.

== Community ==

The '''community''' repository was introduced with Alpine Linux version [https://alpinelinux.org/posts/Alpine-3.3.0-released.html 3.3.0]. ''community'' has a maximum support cycle of 6 months. After that you will need to update to the new release to continue to have support.

= Edge =

''edge'' is the name given to the current [[Aports tree|development tree]] of Alpine Linux. It consists of an APK repository called ''edge'' and contains the latest build of all available Alpine Linux packages. Those packages are updated on a regular basis.

{{Warning|''edge'' is under constant development so be careful using it in production. It is possible that bugs in ''edge'' could cause data loss or could break your system.}}

End users should not use ''edge'' as their main day-to-day workstation or as a productive system. Because ''edge'' is a development branch, many changes are not heavily tested (or tested at all) and packages in ''edge'' can and sometimes do break without warning.

However, testing ''edge'' is a very valuable activity which helps the Alpine Linux development to ensure that the quality of the stable releases is high. Testing ''edge'' is a great way to contribute to the Alpine Linux development.

== Upgrading to edge ==

{{:Include:Upgrading to Edge}}

== Testing ==

The '''testing''' repository was introduced with Alpine Linux ''edge'' development. No support (staging only) and only built for ''edge''. If it stays here long enough it gets moved to unmaintained/purged (gets cleaned up every 6 months).

Before a package can move from ''testing'' to ''main'' or ''community'', the following requirements must be met:

# Package must work correctly, including the init.d script (if provided) and default configuration.
# Packaging must be done correctly, with files installed in the right places, e.g. configs are in <code>/etc/</code> and not in <code>/usr/etc</code>.
# Package dependencies are handled correctly. Abuild can (and should) autodetect shared libs, for example '''sqlite-libs''' provides '''so:libsqlite3.so.0'''. Any package linked to '''sqlite''' should have an automatically (by abuild) added <code>depend=so:libsqlite3.so.0</code> and the user should not have to manually add a <code>depend="sqlite-libs"</code> in the APKBUILD.
# There is a maintainer who claims responsibility for the maintenance of the package and can help fix things if they break in the future.

=== Using the testing repository on stable branches ===

{{Warning|'''Only do this if you're 100% sure what you're doing!''' Installing packages from edge that link to something in ''main'' or ''community'' usually will not work. Alpine does not officially support mixing branches this way.}}

Edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "testing" directory, while also [[Package_management#Repository_pinning|tagging]] the repository, for example:

{{Cat|/etc/apk/repositories|
https://dl-cdn.alpinelinux.org/alpine/v3.16/main
https://dl-cdn.alpinelinux.org/alpine/v3.16/community
@testing https://dl-cdn.alpinelinux.org/alpine/edge/testing
}}

In that case, the tag is <code>@testing</code>, which allows you to pull packages from that repository without potentially messing up your install (too badly):

$ apk add wireguard-go@testing

== Unmaintained ==

{{Expand|Maybe also move this somewhere else?}}

'''unmaintained''' packages are not built.

= See also =

* [[Alpine Linux in a chroot]]
* [http://bugs.alpinelinux.org/ Report Bugs]

[[Category:Development]]
[[Category:Package Manager]]

Repositories

2022-12-09T21:19:37Z

User4708: /* Managing repositories */ added apk update command/note

{{TOC right}}

The Alpine software repositories have three branches:

* '''main''' packages are the software that have direct support and updates from the Alpine core and main team. They also have official special documentation, are always available for all releases and will have substitutions if some are not continued from upstream. Commonly these packages are selected due to their responsibility and stability with respect to upstream availability. Packages from ''community'' or (rarely) ''testing'', that are accepted go to the ''main'' branch.

* '''community''' packages are those made by users in team with the official developers and close to the Alpine package process. They are supported by those user(s) contributions and could end if the user(s) stops; they may also be removed in a future release due to lack of support by upstream authors. Packages from ''testing'' that are accepted go to the ''community'' branch.

* '''testing''' packages are where new packages go. These are made by any contributor to Alpine. Testing has no release linked. The ''testing'' repository is only available on ''edge''. Packages from ''testing'' that are accepted go to the ''community'' branch or (rarely) the ''main'' branch.

= Managing repositories =

To enable a repository, remove the '''#''' in front of the URL along with any blank space.

Example: Disabled
{{cat|/etc/apk/repositories|#http://dl-cdn.alpinelinux.org/alpine/v3.16/community}}

Example: Enabled
{{cat|/etc/apk/repositories|http://dl-cdn.alpinelinux.org/alpine/v3.16/community}}

To edit the repositories, open the <code>/etc/apk/repositories</code> file in a text editor:

{{cmd|# <editor> /etc/apk/repositories}}

The default will look something like:

{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.16/main
#http://dl-cdn.alpinelinux.org/alpine/v3.16/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

After making changes to <code>/etc/apk/repositories</code> you should update the package index using:
{{cmd|# apk update}}

=== Changing repositories to https ===
For better security you should probably change the url's from '''http''' to '''https'''. [https://en.wikipedia.org/wiki/HTTPS#Technical]

{{Note|Some Alpine Linux package mirrors may not support '''https'''. If that is the case, you will need to change mirrors or revert back. You can check if your mirror supports '''https''' on https://mirrors.alpinelinux.org }}

=== Avoid manually changing the repositories file for a new release ===

You can avoid having to manually update the version in <code>/etc/apk/repositories</code> for each Alpine Linux release by changing <code>v3.16</code> to <code>latest-stable</code>.

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
https://dl-cdn.alpinelinux.org/alpine/latest-stable/main
https://dl-cdn.alpinelinux.org/alpine/latest-stable/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Warning|Changing the repositories to <code>latest-stable</code> may initiate unexpected release upgrades.}}

= Release Branches =

There are several release branches for Alpine Linux available at the same time. Each May and November we make a release branch from '''edge'''. The '''main''' repository is typically supported for 2 years and the '''community''' repository is supported until next stable release.

Security fixes beyond that can be made on request when there are patches available.

== Main ==

By default only the '''main''' repository is enabled. ''main'' has a support cycle of 2 years. We also try to limit the amount of packages in ''main'' to only include base system packages, in base you can think of packages which are needed by other packages or are needed to setup a basic system. Packages in ''main'' must '''not''' have dependencies in other repositories.

== Community ==

The '''community''' repository was introduced with Alpine Linux version [https://alpinelinux.org/posts/Alpine-3.3.0-released.html 3.3.0]. ''community'' has a maximum support cycle of 6 months. After that you will need to update to the new release to continue to have support.

=== Enabling the community repository ===

To enable the repository, edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "community" directory.

Its format is:

<nowiki>https://<mirror-server>/alpine/<version>/community</nowiki>

For example, if your mirror is dl-cdn.alpinelinux.org and you're on version 3.16, add the following line to the repositories file:

<nowiki>https://dl-cdn.alpinelinux.org/alpine/v3.16/community</nowiki>

After enabling the community repository, one needs to update the index of available packages with:
{{Cmd|# apk update}}
And then it's possible to install packages from the community repository.

= Edge =

''edge'' is the name given to the current [[Aports tree|development tree]] of Alpine Linux. It consists of an APK repository called ''edge'' and contains the latest build of all available Alpine Linux packages. Those packages are updated on a regular basis.

{{Warning|''edge'' is under constant development so be careful using it in production. It is possible that bugs in ''edge'' could cause data loss or could break your system.}}

End users should not use ''edge'' as their main day-to-day workstation or as a productive system. Because ''edge'' is a development branch, many changes are not heavily tested (or tested at all) and packages in ''edge'' can and sometimes do break without warning.

However, testing ''edge'' is a very valuable activity which helps the Alpine Linux development to ensure that the quality of the stable releases is high. Testing ''edge'' is a great way to contribute to the Alpine Linux development.

== Upgrading to edge ==

{{:Include:Upgrading to Edge}}

== Testing ==

The '''testing''' repository was introduced with Alpine Linux ''edge'' development. No support (staging only) and only built for ''edge''. If it stays here long enough it gets moved to unmaintained/purged (gets cleaned up every 6 months).

Before a package can move from ''testing'' to ''main'' or ''community'', the following requirements must be met:

# Package must work correctly, including the init.d script (if provided) and default configuration.
# Packaging must be done correctly, with files installed in the right places, e.g. configs are in <code>/etc/</code> and not in <code>/usr/etc</code>.
# Package dependencies are handled correctly. Abuild can (and should) autodetect shared libs, for example '''sqlite-libs''' provides '''so:libsqlite3.so.0'''. Any package linked to '''sqlite''' should have an automatically (by abuild) added <code>depend=so:libsqlite3.so.0</code> and the user should not have to manually add a <code>depend="sqlite-libs"</code> in the APKBUILD.
# There is a maintainer who claims responsibility for the maintenance of the package and can help fix things if they break in the future.

=== Enabling the testing repository ===

To enable the repository, edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "testing" directory.

Its format is:

<code><nowiki>https://<mirror-server>/alpine/edge/testing</nowiki></code>

After enabling the testing repository, one needs to update the index of available packages with:
{{Cmd|# apk update}}
And then it's possible to install packages from the testing repository.

=== Using the testing repository on stable branches ===

{{Warning|'''Only do this if you're 100% sure what you're doing!''' Installing packages from edge that link to something in ''main'' or ''community'' usually will not work. Alpine does not officially support mixing branches this way.}}

Edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "testing" directory, while also [[Package_management#Repository_pinning|tagging]] the repository, for example:

{{Cat|/etc/apk/repositories|
https://dl-cdn.alpinelinux.org/alpine/v3.16/main
https://dl-cdn.alpinelinux.org/alpine/v3.16/community
@testing https://dl-cdn.alpinelinux.org/alpine/edge/testing
}}

In that case, the tag is <code>@testing</code>, which allows you to pull packages from that repository without potentially messing up your install (too badly):

$ apk add wireguard-go@testing

== Unmaintained ==

{{Expand|Maybe also move this somewhere else?}}

'''unmaintained''' packages are not built.

= See also =

* [[Alpine Linux in a chroot]]
* [http://bugs.alpinelinux.org/ Report Bugs]

[[Category:Development]]
[[Category:Package Manager]]

Repositories

2022-12-09T21:07:04Z

User4708: /* Overview */ changed overview to Managing repositories and made a few changes to reflect the change.

{{TOC right}}

The Alpine software repositories have three branches:

* '''main''' packages are the software that have direct support and updates from the Alpine core and main team. They also have official special documentation, are always available for all releases and will have substitutions if some are not continued from upstream. Commonly these packages are selected due to their responsibility and stability with respect to upstream availability. Packages from ''community'' or (rarely) ''testing'', that are accepted go to the ''main'' branch.

* '''community''' packages are those made by users in team with the official developers and close to the Alpine package process. They are supported by those user(s) contributions and could end if the user(s) stops; they may also be removed in a future release due to lack of support by upstream authors. Packages from ''testing'' that are accepted go to the ''community'' branch.

* '''testing''' packages are where new packages go. These are made by any contributor to Alpine. Testing has no release linked. The ''testing'' repository is only available on ''edge''. Packages from ''testing'' that are accepted go to the ''community'' branch or (rarely) the ''main'' branch.

= Managing repositories =

To enable a repository, remove the '''#''' in front of the URL along with any blank space.

Example: Disabled
{{cat|/etc/apk/repositories|#http://dl-cdn.alpinelinux.org/alpine/v3.16/community}}

Example: Enabled
{{cat|/etc/apk/repositories|http://dl-cdn.alpinelinux.org/alpine/v3.16/community}}

To edit the repositories, open the <code>/etc/apk/repositories</code> file in a text editor:

{{cmd|# <editor> /etc/apk/repositories}}

The default will look something like:

{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.16/main
#http://dl-cdn.alpinelinux.org/alpine/v3.16/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

=== Changing repositories to https ===
For better security you should probably change the url's from '''http''' to '''https'''. [https://en.wikipedia.org/wiki/HTTPS#Technical]

{{Note|Some Alpine Linux package mirrors may not support '''https'''. If that is the case, you will need to change mirrors or revert back. You can check if your mirror supports '''https''' on https://mirrors.alpinelinux.org }}

=== Avoid manually changing the repositories file for a new release ===

You can avoid having to manually update the version in <code>/etc/apk/repositories</code> for each Alpine Linux release by changing <code>v3.16</code> to <code>latest-stable</code>.

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
https://dl-cdn.alpinelinux.org/alpine/latest-stable/main
https://dl-cdn.alpinelinux.org/alpine/latest-stable/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Warning|Changing the repositories to <code>latest-stable</code> may initiate unexpected release upgrades.}}

= Release Branches =

There are several release branches for Alpine Linux available at the same time. Each May and November we make a release branch from '''edge'''. The '''main''' repository is typically supported for 2 years and the '''community''' repository is supported until next stable release.

Security fixes beyond that can be made on request when there are patches available.

== Main ==

By default only the '''main''' repository is enabled. ''main'' has a support cycle of 2 years. We also try to limit the amount of packages in ''main'' to only include base system packages, in base you can think of packages which are needed by other packages or are needed to setup a basic system. Packages in ''main'' must '''not''' have dependencies in other repositories.

== Community ==

The '''community''' repository was introduced with Alpine Linux version [https://alpinelinux.org/posts/Alpine-3.3.0-released.html 3.3.0]. ''community'' has a maximum support cycle of 6 months. After that you will need to update to the new release to continue to have support.

=== Enabling the community repository ===

To enable the repository, edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "community" directory.

Its format is:

<nowiki>https://<mirror-server>/alpine/<version>/community</nowiki>

For example, if your mirror is dl-cdn.alpinelinux.org and you're on version 3.16, add the following line to the repositories file:

<nowiki>https://dl-cdn.alpinelinux.org/alpine/v3.16/community</nowiki>

After enabling the community repository, one needs to update the index of available packages with:
{{Cmd|# apk update}}
And then it's possible to install packages from the community repository.

= Edge =

''edge'' is the name given to the current [[Aports tree|development tree]] of Alpine Linux. It consists of an APK repository called ''edge'' and contains the latest build of all available Alpine Linux packages. Those packages are updated on a regular basis.

{{Warning|''edge'' is under constant development so be careful using it in production. It is possible that bugs in ''edge'' could cause data loss or could break your system.}}

End users should not use ''edge'' as their main day-to-day workstation or as a productive system. Because ''edge'' is a development branch, many changes are not heavily tested (or tested at all) and packages in ''edge'' can and sometimes do break without warning.

However, testing ''edge'' is a very valuable activity which helps the Alpine Linux development to ensure that the quality of the stable releases is high. Testing ''edge'' is a great way to contribute to the Alpine Linux development.

== Upgrading to edge ==

{{:Include:Upgrading to Edge}}

== Testing ==

The '''testing''' repository was introduced with Alpine Linux ''edge'' development. No support (staging only) and only built for ''edge''. If it stays here long enough it gets moved to unmaintained/purged (gets cleaned up every 6 months).

Before a package can move from ''testing'' to ''main'' or ''community'', the following requirements must be met:

# Package must work correctly, including the init.d script (if provided) and default configuration.
# Packaging must be done correctly, with files installed in the right places, e.g. configs are in <code>/etc/</code> and not in <code>/usr/etc</code>.
# Package dependencies are handled correctly. Abuild can (and should) autodetect shared libs, for example '''sqlite-libs''' provides '''so:libsqlite3.so.0'''. Any package linked to '''sqlite''' should have an automatically (by abuild) added <code>depend=so:libsqlite3.so.0</code> and the user should not have to manually add a <code>depend="sqlite-libs"</code> in the APKBUILD.
# There is a maintainer who claims responsibility for the maintenance of the package and can help fix things if they break in the future.

=== Enabling the testing repository ===

To enable the repository, edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "testing" directory.

Its format is:

<code><nowiki>https://<mirror-server>/alpine/edge/testing</nowiki></code>

After enabling the testing repository, one needs to update the index of available packages with:
{{Cmd|# apk update}}
And then it's possible to install packages from the testing repository.

=== Using the testing repository on stable branches ===

{{Warning|'''Only do this if you're 100% sure what you're doing!''' Installing packages from edge that link to something in ''main'' or ''community'' usually will not work. Alpine does not officially support mixing branches this way.}}

Edit the file <code>/etc/apk/repositories</code> and add (or uncomment) a line that points to the "testing" directory, while also [[Package_management#Repository_pinning|tagging]] the repository, for example:

{{Cat|/etc/apk/repositories|
https://dl-cdn.alpinelinux.org/alpine/v3.16/main
https://dl-cdn.alpinelinux.org/alpine/v3.16/community
@testing https://dl-cdn.alpinelinux.org/alpine/edge/testing
}}

In that case, the tag is <code>@testing</code>, which allows you to pull packages from that repository without potentially messing up your install (too badly):

$ apk add wireguard-go@testing

== Unmaintained ==

{{Expand|Maybe also move this somewhere else?}}

'''unmaintained''' packages are not built.

= See also =

* [[Alpine Linux in a chroot]]
* [http://bugs.alpinelinux.org/ Report Bugs]

[[Category:Development]]
[[Category:Package Manager]]