Include:Setup your system and account for building packages: Difference between revisions

From Alpine Linux
(That's what sudo -e is for.)
(Use doas instead of sudo)
Line 1: Line 1:
The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. Install those packages now:  
The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. We'll also install doas to perform superuser operations, and nano to allow us to edit text:


{{Cmd|apk add alpine-sdk sudo}}
{{Cmd|apk add alpine-sdk doas nano}}


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:
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.
 
{{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.
The [[Aports_tree|aports tree]] is in git so before we clone the it, let's configure git.
Line 30: Line 18:
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:
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 -e /etc/abuild.conf}}
{{Cmd|doas nano /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.
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.
To use 'abuild -r' command to install dependency packages automatically.
{{Cmd|sudo addgroup <yourusername> abuild}}
{{Cmd|doas 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:
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
{{Cmd|doas mkdir -p /var/cache/distfiles
sudo chmod a+w /var/cache/distfiles}}
doas chmod a+w /var/cache/distfiles}}


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


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


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

Revision as of 19:46, 25 November 2021

The alpine-sdk is a metapackage that pulls in the most essential packages used to build new packages. We'll also install doas to perform superuser operations, and nano to allow us to edit text:

apk add alpine-sdk doas nano

This would be a good time to 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 is in git so before we clone the it, let's configure git.

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.

git clone https://gitlab.alpinelinux.org/alpine/aports

Before we start creating or modifying APKBUILD files, we need to setup abuild for our system and user. Edit the file abuild.conf to your requirements:

doas nano /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.

doas addgroup <yourusername> abuild

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

doas mkdir -p /var/cache/distfiles doas chmod a+w /var/cache/distfiles

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

doas chgrp abuild /var/cache/distfiles doas 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 script for abuild with the command:

abuild-keygen -a -i

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=Include:Setup_your_system_and_account_for_building_packages&oldid=20384"