Alpine Linux - User contributions [en]

Flatpak

2022-10-16T13:50:36Z

Saltedcoffii: /* Links */ Fix Winepak link (winepak.org isn't working)

{{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/Post_installation#Repositories Post Installation - 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]]

Include:Setup your system and account for building packages

2022-04-28T05:53:46Z

Saltedcoffii:

The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. Also install and configure a way to elevate privileges, such as sudo or doas, and an editor, such as vi, nano, micro.

{{Cmd|# apk add alpine-sdk}}

This would be a good time to [[Setting_up_a_new_user|create a normal user account for you to work in]]. To make life easier later, it's a good idea to add this user to the wheel group; operations that require superuser privileges can now be done with sudo or doas.

The [[Aports_tree|aports tree]] is in git so before we clone the it, let's configure git.

{{Cmd|$ git config --global user.name "Your Full Name"
$ git config --global user.email "your@email.address"}}

Read carefully [[Development using git]] to grasp basic Git operations and how to configure for sending email patches.

Now we can clone the [[Aports_tree|aports tree]].

{{Cmd|$ git clone https://gitlab.alpinelinux.org/alpine/aports}}

Before we start creating or modifying [[APKBUILD_Reference|APKBUILD]] files, we need to setup abuild for our system and user. Edit the file {{Path|abuild.conf}} to your requirements.

Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.

To use 'abuild -r' command to install dependency packages automatically.
{{Cmd|# addgroup <yourusername> abuild}}

We also need to prepare the location where the build process caches files when they are downloaded. By default this is {{Path|/var/cache/distfiles/}}. To create this directory and ensure that it is writeable, enter the following commands:

{{Cmd|# mkdir -p /var/cache/distfiles}}
{{Cmd|# chmod a+w /var/cache/distfiles}}

As an alternative to the second command, you can add yourself to the abuild group:

{{Cmd|# chgrp abuild /var/cache/distfiles}}
{{Cmd|# chmod g+w /var/cache/distfiles}}

{{Note|Remember to logout and login again for the group change to have effect.}}

The last step is to configure the security keys with the [[Abuild-keygen|abuild-keygen]] script for [[Abuild|abuild]] with the command:

{{Cmd|# abuild-keygen -a -i}}

[[Category:Development]]

Include:Setup your system and account for building packages

2022-04-27T23:56:48Z

Saltedcoffii: Fix formatting

The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. Also install and configure a way to elevate privileges, such as sudo or doas, and an editor, such as vi, nano, micro.

{{Cmd|# apk add alpine-sdk}}

This would be a good time to [[Setting_up_a_new_user|create a normal user account for you to work in]]. To make life easier later, it's a good idea to add this user to the wheel group; operations that require superuser privileges can now be done with doas.

The [[Aports_tree|aports tree]] is in git so before we clone the it, let's configure git.

{{Cmd|$ git config --global user.name "Your Full Name"
$ git config --global user.email "your@email.address"}}

Read carefully [[Development using git]] to grasp basic Git operations and how to configure for sending email patches.

Now we can clone the [[Aports_tree|aports tree]].

{{Cmd|$ git clone https://gitlab.alpinelinux.org/alpine/aports}}

Before we start creating or modifying [[APKBUILD_Reference|APKBUILD]] files, we need to setup abuild for our system and user. Edit the file {{Path|abuild.conf}} to your requirements.

Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.

To use 'abuild -r' command to install dependency packages automatically.
{{Cmd|# addgroup <yourusername> abuild}}

We also need to prepare the location where the build process caches files when they are downloaded. By default this is {{Path|/var/cache/distfiles/}}. To create this directory and ensure that it is writeable, enter the following commands:

{{Cmd|# mkdir -p /var/cache/distfiles}}
{{Cmd|# chmod a+w /var/cache/distfiles}}

As an alternative to the second command, you can add yourself to the abuild group:

{{Cmd|# chgrp abuild /var/cache/distfiles}}
{{# chmod g+w /var/cache/distfiles}}

{{Note|Remember to logout and login again for the group change to have effect.}}

The last step is to configure the security keys with the [[Abuild-keygen|abuild-keygen]] script for [[Abuild|abuild]] with the command:

{{Cmd|# abuild-keygen -a -i}}

[[Category:Development]]

Include:Setup your system and account for building packages

2022-04-27T23:37:14Z

Saltedcoffii: This wiki page forced people to use doas and nano, when there are other permission elevators and editors. I removed all mentions of nano and just instructed the reader to edit the file, and changed commands to $ and #.

The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. Also install and configure a way to elevate privileges, such as sudo or doas, and an editor, such as vi, nano, micro.

{{Cmd|# apk add alpine-sdk}}

This would be a good time to [[Setting_up_a_new_user|create a normal user account for you to work in]]. To make life easier later, it's a good idea to add this user to the wheel group; operations that require superuser privileges can now be done with doas.

The [[Aports_tree|aports tree]] is in git so before we clone the it, let's configure git.

{{Cmd|$ git config --global user.name "Your Full Name"
$ git config --global user.email "your@email.address"}}

Read carefully [[Development using git]] to grasp basic Git operations and how to configure for sending email patches.

Now we can clone the [[Aports_tree|aports tree]].

{{Cmd|$ git clone https://gitlab.alpinelinux.org/alpine/aports}}

Before we start creating or modifying [[APKBUILD_Reference|APKBUILD]] files, we need to setup abuild for our system and user. Edit the file {{Path|abuild.conf}} to your requirements.

Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.

To use 'abuild -r' command to install dependency packages automatically.
{{Cmd|# addgroup <yourusername> abuild}}

We also need to prepare the location where the build process caches files when they are downloaded. By default this is {{Path|/var/cache/distfiles/}}. To create this directory and ensure that it is writeable, enter the following commands:

{{Cmd|# mkdir -p /var/cache/distfiles
# chmod a+w /var/cache/distfiles}}

As an alternative to the second command, you can add yourself to the abuild group:

{{Cmd|# chgrp abuild /var/cache/distfiles
# chmod g+w /var/cache/distfiles}}

{{Note|Remember to logout and login again for the group change to have effect.}}

The last step is to configure the security keys with the [[Abuild-keygen|abuild-keygen]] script for [[Abuild|abuild]] with the command:

{{Cmd|# abuild-keygen -a -i}}

[[Category:Development]]

Include:Setup your system and account for building packages

2020-11-17T21:41:10Z

Saltedcoffii: change `vi` to $EDITOR to use the user's preferred editor.

The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. Install those packages now:

{{Cmd|apk add alpine-sdk}}

This would be a good time to create a normal user account for you to work in. (You weren't going to develop as root now, were you!) To create the user:

{{Cmd|adduser <yourusername>}}

To make life easier later, it's a good idea to add this user to {{Path|/etc/sudoers}}. Append the line

<yourusername> ALL=(ALL) ALL

using the command:

{{Cmd|visudo}}

Now logout of the root account, and login as <yourusername>. From here on everything can be done in a normal user account, and operations that require superuser privileges can be done with sudo.

The [[Aports_tree|aports tree]] is in git so before we clone the it, let's configure git.

{{Cmd|git config --global user.name "Your Full Name"
git config --global user.email "your@email.address"}}

Read carefully [[Development using git]] to grasp basic Git operations and how to configure for sending email patches.

Now we can clone the [[Aports_tree|aports tree]].

NOTE: You can also clone aports from our github https://github.com/alpinelinux/aports

{{Cmd|git clone git://git.alpinelinux.org/aports}}

Before we start creating or modifying [[APKBUILD_Reference|APKBUILD]] files, we need to setup abuild for our system and user. Edit the file {{Path|abuild.conf}} to your requirements:

{{Cmd|sudo $EDITOR /etc/abuild.conf}}

Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.

To use 'abuild -r' command to install dependency packages automatically.
{{Cmd|sudo addgroup <yourusername> abuild}}

We also need to prepare the location where the build process caches files when they are downloaded. By default this is {{Path|/var/cache/distfiles/}}. To create this directory and ensure that it is writeable, enter the following commands:

{{Cmd|sudo mkdir -p /var/cache/distfiles
sudo chmod a+w /var/cache/distfiles}}

As an alternative to the second command, you can add yourself to the abuild group:

{{Cmd|sudo chgrp abuild /var/cache/distfiles
sudo chmod g+w /var/cache/distfiles}}

{{Note|Remember to logout and login again for the group change to have effect.}}

The last step is to configure the security keys with the [[Abuild-keygen|abuild-keygen]] script for [[Abuild|abuild]] with the command:

{{Cmd|abuild-keygen -a -i}}

[[Category:Development]]