Alpine Linux - User contributions [en]

Repositories

2024-02-17T10:57:53Z

Romw314: Add setup-apkrepos cmd.

{{TOC right}}

There are three repositories:

* '''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'' can be accepted into the ''main'' repository.

* '''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'' repository.

* '''testing''' is 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'' repository or (rarely) the ''main'' repository.

= Managing repositories =

The package repositories that <code>apk</code> uses to retrieve package files for installation are specified in file {{path|/etc/apk/repositories}}. Each line of this file specifies the location of a package repository, and optionally a tag. Lines that start with a hash character (#) are ignored.

The location may be an <code>http://</code> or <code>https://</code> URL, or the path to a directory on the local filesystem. A [[Package_management#Repository_pinning|tagged]] repository is prefixed with the <code>@tag</code> specifier, followed by a space and the repository location.

The default will look something like:

{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v{{#expr:{{AlpineLatest}}}}/main
http://dl-cdn.alpinelinux.org/alpine/v{{#expr:{{AlpineLatest}}}}/community}}

To automatically configure {{path|/etc/apk/repositories}}, use:
{{cmd|# [[Alpine setup scripts#setup-apkrepos|setup-apkrepos]] -cf}}

After making changes to {{path|/etc/apk/repositories}} 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 {{path|/etc/apk/repositories}} for each Alpine Linux release by changing {{ic|v{{#expr:{{AlpineLatest}}}}}}</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 ==

''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 {{path|/etc/apk/repositories}} 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/v{{#expr:{{AlpineLatest}}}}/main
https://dl-cdn.alpinelinux.org/alpine/v{{#expr:{{AlpineLatest}}}}/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

= See also =

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

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

Migrate SVN to Git

2024-02-17T10:46:58Z

Romw314: Fix code without <code>, fix shouldnt => shouldn't.

{{obsolete|This document describes how to migrate an SVN repository to git. This is for historical reference.}}

== Init git repository ==
Create a temp work area.

{{Cmd|mkdir proj-tmp}}

Init the git repository. If your svn repo does not have the standard trunk branches and tags dirs you shouldn't use the <code>--stdlayout</code>. You can also use <code>-T trunk -b branches -t tags</code>.

{{Cmd|cd proj-tmp
git svn init <nowiki>svn://svn.alpinelinux.org/proj</nowiki> --stdlayout}}

== Create user mapping ==
Start with creating a users.txt file where the svn users are mapped to an email address for git.

{{Cmd|<nowiki>echo "ncopa = Natanael Copa <ncopa@example.com>" > users.txt</nowiki>}}

== Connect the user mapping ==
Connect the users.txt to the empty git repository so users are remapped.

{{Cmd|git config svn.authorsfile ../users.txt}}

== Fetch SVN repository ==
This might take some time.

{{Cmd|git fetch}}

== Upload the Git repository ==

Now we can create a bare repository and upload it to dev.alpinelinux.org/gitroot.

{{Cmd|cd ..
git clone --bare proj-tmp proj.git
scp -r proj.git dev.alpinelinux.org:/~}}

[[Category:Development]]
[[Category:Git]]

KDE

2024-02-16T12:05:24Z

Romw314: Add plasma pkg 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-desktop-meta|arch=}} package isn't available for the <code>ppc64le</code>, <code>s390x</code>, <code>armhf</code>, or <code>riscv64</code> architectures due to the {{Pkg|kdeplasma-addons|arch=}} dependency not being available there. However, the rest of Plasma may be installed separately to potentially get a functional desktop.}}
 

== Prerequisites ==

* [[Installation|Install]] Alpine Linux
* Create a [[Setting_up_a_new_user#Creating_a_new_user|user account]]
* Enable the <code>community</code> [[Repositories#Managing_repositories|repository]]
* For users interested in Xorg as opposed to Wayland, install the [[Alpine_setup_scripts#setup-xorg-base|Xorg base packages]]
* [[D-Bus#Installation|Install and configure D-Bus]]
* [[Elogind#Installation|Install and configure Elogind]]
* Wayland users: Install package {{pkg|xf86-input-libinput|arch=}}

 

== Installation ==

The following command will install the Plasma desktop as specified by the {{Pkg|plasma|arch=}} metapackage, including the {{Pkg|sddm|arch=}} display manager and other assorted niceties.

{{Cmd|# apk add {{Pkg|plasma|arch=}}}}

{{:Include:Setup_Device_Manager}}

{{Note|'''polkit''' and '''udev''' are optional services for authentication and device management respectively. While KDE will function without these services enabled, some functionality may be missing or incomplete.}}

 

== 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:

{{Note|Most of these are not available on <code>ppc64le</code> or <code>s390x</code>.}}
* {{Pkg|kde-applications-accessibility|arch=}}
* {{Pkg|kde-applications-admin|arch=}}
* {{Pkg|kde-applications-base|arch=}}
* {{Pkg|kde-applications-edu|arch=}}
* {{Pkg|kde-applications-games|arch=}}
* {{Pkg|kde-applications-graphics|arch=}}
* {{Pkg|kde-applications-multimedia|arch=}}
* {{Pkg|kde-applications-network|arch=}}
* {{Pkg|kde-applications-pim|arch=}}
* {{Pkg|kde-applications-sdk|arch=}}
* {{Pkg|kde-applications-utils|arch=}}
* {{Pkg|kde-applications-webdev|arch=}}

 

== Starting Plasma ==

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

=== Using a display manager ===

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

Make sure you enable and start the SDDM service.

{{Cmd|rc-update add sddm
rc-service sddm start
}}

* 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|arch=}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. To start X:
{{Cmd|xinit}}

For the Wayland session run
{{Cmd|XDG_SESSION_TYPE{{=}}wayland dbus-run-session startplasma-wayland}}

 

== See also ==
* [[Installation#Post-Installation|Post installation]]
* [[Flatpak]]
* [https://wiki.archlinux.org/title/KDE KDE - Archwiki]

[[Category:Desktop]]
[[Category:Desktop Environments]]
[[Category:Wayland]]