The Battle for Wesnoth Wiki - User contributions [en]

WesnothRepository

2021-11-10T00:49:26Z

Clavi: /* Push access */ replaced ssh key type with modern ed25519, replaced mentions of "OSX" with "macOS"

{{Compiling Wesnoth}}

'''The <cite>Battle for Wesnoth</cite> code-base''' is stored in a '''<dfn>version control repository</dfn>'''. Version control allows the entire development team to edit files concurrently. The version control software tracks revisions, stores a record of all edits, and prevents simultaneous editing from causing clashes. All changes are stored in the version control repository.

When a release is planned, the current set of the files in the repository is ''"frozen"'', given a version number, and shipped out to the world at large. Then, as files continue to be edited by the developers, the repository code advances past that point. The repository (or "'''<dfn>repo</dfn>'''") version is by definition the most up-to-date version of the code.

The <cite>Wesnoth</cite> repository is a '''Git''' repository and is hosted on '''GitHub''':

{{FeaturedURL|https://github.com/wesnoth/wesnoth}}

== What is <cite>Git</cite>? ==

{{SideBox|heading=Are you a newcomer to Git or GitHub who would like to work on <cite>Wesnoth</cite>?|If so, you may find iceiceice's <cite>[[Git for Wesnoth Crash Course]]</cite> to be a useful read -- while <cite>WesnothRepository</cite> is also beginner-focused, it's not as extensive as iceiceice's <cite>Crash Course</cite>).}}

<dfn>Git</dfn> is the most widely used open-source version-control system. You can learn more about it at its website:

{{FeaturedURL|https://git-scm.com}}

Git replaced '''Subversion (<dfn>SVN</dfn>)''' as <cite>Wesnoth</cite>'s version-control system in March 2013. Subversion had, itself, previously replaced an older program, '''Concurrent Versioning System (<dfn>CVS</dfn>)''', in 2005. These earlier systems have left a few traces in the version history which you might encounter; some older documentation and a few files refer to them.

== Browse the code ==

{{SideBox|heading=Want a {{abbr|GUI|Graphical User Interface}} for Git?|[https://www.syntevo.com/smartgit/ <cite>SmartGit</cite>] is cross-platform and supposedly powerful, and the {{abbr|IDEs|Integrated Development Environments}} [https://www.qt.io/download-open-source/ <cite>Qt Creator</cite>] and <cite>Microsoft Visual Studio</cite> provide Git GUIs. <em><strong>However</strong></em>, the official Git command-line program is <em>by far</em> the easiest Git program to get help with -- you may well have trouble finding people who can help you with a Git GUI.}}

You can use a Web browser to view the source code at the following Web address:
{{FeaturedURL|https://github.com/wesnoth/wesnoth}}

There are currently two main streams of development ("<dfn>branches</dfn>"): the '''master''' branch (1.15.x), and the '''stable''' branch (1.14.x). (1.12.x is now '''oldstable'''.) Most other branches are only used for a short time to do some testing without disturbing the main development.

== Download ==

To '''''clone''''' a copy of the repository into a directory named "''wesnoth''", run this command:

'''>''' git clone "<nowiki>https://github.com/wesnoth/wesnoth.git</nowiki>" wesnoth

{{SideBox|style=font-size:.75em;line-height:1.6|heading=Technical aside: Git transport protocols|There are other '''<dfn>transport protocols</dfn>''', in addition to '''Hypertext Transfer Protocol Secure (<dfn>HTTPS</dfn>)''', over which one can clone a Git repository from GitHub, including:

* '''Secure Shell (<dfn>SSH</dfn>)''' ("<code><nowiki>ssh://git@github.com/wesnoth/wesnoth.git</nowiki></code>", or "<code>git@github.com:wesnoth/wesnoth.git</code>"), which provides a bit more security, and can be more convenient for developers, but needs to be set up first (see the "Push access" section, below).
* Git's '''native transport''' protocol ("<code><nowiki>git://github.com/wesnoth/wesnoth.git</nowiki></code>"), which <em>may</em> be somewhat faster than HTTPS (though GitHub uses a faster '''"smart" HTTPS''' transport), but is <em><strong>insecure</strong></em> and should be used (if one <em>must</em> use it) with caution (<em>check the commit hashes!</em>).

'''A more detailed explanation''' is available [https://gist.github.com/grawity/4392747 here].}}

<small style="font-size: 95%">('''Note:''' the "'''>'''" sigil represents a command prompt; '''don't type it in'''.)</small>

=== FAQ ===

'''Q: The repository is about three gigabytes large, and my Internet connection is not stable enough to reliably download it. What should I do?'''

'''A:''' https://stackoverflow.com/questions/9268378/how-do-i-clone-a-large-git-repository-on-an-unreliable-connection

# Use a download manager to download the directory "https://github.com/wesnoth/wesnoth.git", in one or more sessions.
# Put this "''wesnoth.git''" directory, which is the internals of the <cite>Wesnoth</cite> repository, in a new, empty directory.
# Rename the "''wesnoth.git''" directory to "''.git''".
# Finally, run these commands in the directory that contains the "''.git''" directory:

'''>''' git remote add remote "<nowiki>https://github.com/wesnoth/wesnoth.git</nowiki>"
'''>''' git reset --hard HEAD

The first command links your local repository to the upstream repository; the second <dfn>checks out</dfn> a <dfn>working tree</dfn> (i.e., copies the files out of the "''.git''" directory into a form that you can use).

'''Alternative:''' This will make a shallow clone and allow you to fetch additional history as desired.
# Start by using a clone command
# Run a git fetch command with an increased depth, such as "git fetch --depth=2000"
# Continue to run additional fetch commands, each time increasing the depth, based on what your connection can handle. As of this writing, the max depth is around 60-70K.
# When an increase in depth no longer brings additional data, verify you have a complete repository by using "git fetch --unshallow"
# To fix the single branch checkout aspect, use git config and fetch commands.
A sample sequence is shown below. You may want to use smaller depth increases (i.e.,2-5K) based on your connection speed and reliability.
'''>''' git clone --depth 1 "<nowiki>https://github.com/wesnoth/wesnoth.git</nowiki>" wesnoth
'''>''' git fetch --depth=10000
'''>''' git fetch --depth=20000
'''>''' git fetch --depth=30000
'''>''' git fetch --depth=40000
'''>''' git fetch --depth=50000
'''>''' git fetch --depth=60000
'''>''' git fetch --depth=70000
'''>''' git fetch --unshallow
'''>''' git config remote.origin.fetch "<nowiki>+refs/heads/*:refs/remotes/origin/*</nowiki>"
'''>''' git fetch origin

'''Q: I don't want any alternate branches or repository history. How could I avoid downloading that?'''

'''A:''' This simply requires a more elaborate command. For example, to only download the last revision of the 1.14 branch, and store it in a directory named "''wesnoth-1.14-single-branch-test''":

'''>''' git clone --branch 1.14 --single-branch --depth 1 "<nowiki>https://github.com/wesnoth/wesnoth.git</nowiki>" wesnoth-1.14-single-branch-test

Example results:

'''>''' git clone --branch 1.14 --single-branch --depth 1 "<nowiki>https://github.com/wesnoth/wesnoth.git</nowiki>" wesnoth-1.14-single-branch-test
Cloning into 'wesnoth-1.14-single-branch-test'...
remote: Counting objects: 20751, done.
remote: Compressing objects: 100% (20087/20087), done.
remote: Total 20751 (delta 968), reused 11881 (delta 416), pack-reused 0
Receiving objects: 100% (20751/20751), 444.98 MiB | 636.00 KiB/s, done.
Resolving deltas: 100% (968/968), done.
Checking out files: 100% (20369/20369), done.
'''>''' du -sh wesnoth-1.14-single-branch-test ''# "du" means "disk usage".''
1.3G wesnoth-1.14-single-branch-test

However, for development and testing, it is often better to have some of the repository history, so that you can quickly check out older versions of the repository to pin down a bug.

== Push access ==

For '''<dfn>push access</dfn>''' (the capability to ''push'' changes from your local repository) to our ''upstream'' repository on GitHub, you must have an account on GitHub, which must be registered as part of the [https://github.com/wesnoth ''Battle for Wesnoth''] organization.

It may be convenient to use Git's '''Secure Shell (SSH) transport protocol''', so that you needn't either enter your username and password each time you push commits, or insecurely store those credentials in an unencrypted configuration file. To use the SSH transport, you will need to generate an SSH '''''key pair''''' with a command like (on Unix descendent operating systems, including Linux distributions and Apple macOS, at least) this:

'''>''' ssh-keygen -t ed25519 -f "<var><file></var>" -C "<var><your name></var>'s SSH key for GitHub"

On a typical Linux distribution or on Apple macOS, <var><file></var> would be, e.g., "''~/.ssh/id-key-for-github''".

Once you have generated an SSH key pair, put the following into your SSH configuration file (on Unix descendent systems, this is generally "''~/.ssh/config''"):

Host github.com
IdentityFile <var><file></var>

Then register the key with GitHub, by going to [https://github.com/settings/ssh <https://github.com/settings/ssh>], selecting "Add SSH key", and pasting the contents of the '''''public key''''' file (<var><file></var>, but with a "''.pub''" extension) into the "Key" field.

Then, if you have not yet cloned the repository, clone it via SSH:

'''>''' git clone "<nowiki>ssh://git@github.com/wesnoth/wesnoth.git</nowiki>" wesnoth

If you have already cloned the repository, you can set it to use SSH transfer:

'''>''' git remote set-url origin "<nowiki>ssh://git@github.com/wesnoth/wesnoth.git</nowiki>"

=== Force-pushing policy ===

A '''<dfn>forced push</dfn>''' rewrites a branch tip to point to a new commit without checking first whether the new commit is a descendant of the current tip. This effectively allows you to rewrite the commit history of a branch, which may be useful when working with pull requests from your own [[#Push_to_your_own_fork|personal fork]].

'''>''' git push --force fork <var><branch name></var>

However, for a public repository depended upon by more than a handful people like any of the <cite>Wesnoth</cite> repositories at [https://github.com/wesnoth <https://github.com/wesnoth>], force-pushing becomes a serious inconvenience that may have negative consequences in some cases, if history is lost in the process. For this reason, <strong>force-pushing to the upstream <cite>Wesnoth</cite> repositories is <em>NOT allowed</em> unless specifically authorized by the repository administrators in order to resolve an urgent issue</strong>.

== Update ==

Do this from inside the ''wesnoth'' directory:

'''>''' git pull

== Reviewing your changes ==

Before committing, it's always wise to run:

'''>''' git diff

and look at the output. Some kinds of mistakes that are hard to see embedded in all the code you have modified are more easily spotted in the isolated diff lines.

== Generating patches ==

Under Git on a Unix-like operating system, you'll typically do

'''>''' git format-patch HEAD~1..HEAD

or something similar; "HEAD~1" may be replaced by a hash or symbolic reference to any earlier revision. This will produce one or more patch files, numbered and ending with the extension ".patch". See [[PatchSubmissionGuidelines]] for more on how to get these merged into the public repository.

== Push to your own fork ==

If you have an account on GitHub, you can fork the repository and add your fork as a remote of your clone.

'''>''' git remote add fork git@github.com:YOUR_USERNAME/wesnoth.git

You can then push your branches to your fork:

'''>''' git push fork branch_name

Or, if you want to push one branch in your local repository to another in the remote repository:

'''>''' git push fork local_branch_name:remote_branch_name

You can then create pull requests from your branches in GitHub’s Web interface.

== See Also ==

* [[Git for Wesnoth Crash Course]]

[[Category:Development]]

WesnothBinariesLinux

2021-11-09T23:57:30Z

Clavi: there is no Pardus entry anymore, also removed superfluous spacer lines

{{Translations}}

<div class="tright"> __TOC__ </div>

Not all distributions carry the latest stable or development releases. If you want to make sure you are running the newest official version of Wesnoth from either branch, either get the sources from the [[Download]] page and [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md compile them yourself] or use the nightly flatpak below.

== Flatpak ==
A nightly flatpak of Wesnoth's development branch is available. Instructions for getting it can be found [https://forums.wesnoth.org/viewtopic.php?f=5&t=47872 here].

A flatpak of the current stable release(1.14) is also available [https://flathub.org/apps/details/org.wesnoth.Wesnoth here].

== Arch Linux ==
* The latest stable version can be installed from the [community] repository: <code>pacman -S wesnoth</code>
* There's a wesnoth-devel package for development releases in [https://aur.archlinux.org/packages/wesnoth-devel/ the AUR].

== Debian ==
* [http://packages.debian.org/wesnoth Official packages] including the development releases. If you want a different version, you need to explicitly request which branch you want, e.g. [http://packages.debian.org/wesnoth-1.12 1.12] (stretch), or [http://packages.debian.org/wesnoth-1.14 1.14] (buster, bullseye, and sid)
* [http://backports-master.debian.org/ backports.debian.org] offers the latest stable wesnoth releases, albeit only backported to stretch at this time. For more info on Debian backports, click [http://wiki.debian.org/Backports here].

===Command-line install===
To install Wesnoth, run the following to pull in everything:
aptitude install wesnoth wesnoth-music

===Compiling===

If you want to run a newer release than the ones provided in the Debian repositories, or an unreleased version from the [[WesnothRepository|Git repository]], you will have to build it from source. See [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md Compiling Wesnoth] for more details.

To install Wesnoth's dependencies if you have Debian's source repositories enabled in your config, you can just use apt's <code>build-dep</code> command with the package that best matches the version you are trying to build:

# Stable version
aptitude build-dep wesnoth
# Development version
aptitude build-dep wesnoth-1.14

'''Note:''' If you have already installed an older version of Wesnoth, you should uninstall it first by running:

# Stable version
aptitude purge wesnoth
# Development version
aptitude purge wesnoth-1.14

Bear in mind that this will '''not''' remove downloaded data or saved games stored in your [[EditingWesnoth#The_user_data_directory|home directory]].

Additionally, build-dep will not install libssl-dev automatically due to a Debian patch to use WolfSSL instead due to a licence incompatibility with OpenSSL, so you will need to install that manually. This will likely be resolved within the next couple of years once OpenSSL 3 comes into use since that version will resolve the license incompatibility.

== Ubuntu ==

[http://apt.ubuntu.com/p/wesnoth Click here] to install the latest version of the <code>wesnoth</code> packaged for your release. Alternatively, search for "wesnoth" in the ''Ubuntu Software Center'' or use following command:

sudo apt-get install wesnoth

===Available Versions===

Different releases of Ubuntu provide different versions of Wesnoth in their repositories. Often, this version will be older than the most current Wesnoth.

{| class="wikitable"
|-
! Release
! Packaged Version
|-
| 20.04 LTS (Focal)
| 1.14.9
|-
| 19.10 (Eoan)
| 1.14.7
|-
| 19.04 (Disco)
| 1.14.6
|-
| 18.10 (Cosmic)
| 1.14.4
|-
| 18.04 LTS (Bionic)
| 1.12.6
|-
| 16.04 LTS (Xenial)
| 1.12.5
|}

== Fedora ==
Battle for Wesnoth is included in [http://koji.fedoraproject.org/koji/packageinfo?packageID=4097 Fedora]. The current version of Battle for Wesnoth is available for ARMv7HL, AArch64, ppc64le, s390x, x86, and x86_64 architectures. If you have problems with these packages, or other questions, please contact the Fedora maintainer [mailto:klember@redhat.com Kalev Lember].

To install from command-line, simply run:
dnf install wesnoth wesnoth-tools wesnoth-server

== Gentoo ==
To install the game only, run the following as root:
emerge wesnoth

To install the game and the server, add 'server' to your USE flags, then run emerge as above.

Note: Gentoo currently operates as a rolling-release, updated approximately weekly.

To install the latest unstable version (when available), add the following line to your /etc/portage/package.keywords file before running the emerge command:

games-strategy/wesnoth ~*

The ebuild is currently maintained by [https://wiki.gentoo.org/wiki/Project:Games the Gentoo Games Project]

== Mageia / Rosa Linux / OpenMandriva Lx ==

To install the latest stable version (as root):

urpmi wesnoth

For the development version (Rosa Linux and OpenMandriva Lx only, as root):

urpmi wesnoth-unstable

You can also use the GUI package manager RPMDrake (in the Control Centre).

To install latest Battle for Wesnoth version available you need to enable the following repository using the Control Centre:

{|align="left" border="1"
!align="left"|Distribution
!align="left"|Repository for wesnoth
!align="left"|Repository for wesnoth-unstable
|-
|Rosa Linux Desktop / OpenMandriva Lx
|contrib release
|contrib updates
|-
|Rosa Linux LTS
|contrib updates
|contrib updates
|-
|Mageia
|core release
|N/A
|}




==openSUSE==

These are builds of The Battle For Wesnoth for several versions of openSUSE, made for both i386 and x86_64 architectures.

The openSUSE packages are maintained by [https://build.opensuse.org/package/view_file/openSUSE:Factory/wesnoth/wesnoth.changes multiple contributors].

===Install using One-Click Installation===

Use the correct link for your version of openSUSE:

* openSUSE Tumbleweed (rolling release) [https://software.opensuse.org/ymp/openSUSE:Factory/standard/wesnoth.ymp One-Click Install]
* openSUSE Leap 15.3 (fixed release) [https://software.opensuse.org/ymp/openSUSE:Backports:SLE-15-SP3/standard/wesnoth.ymp One-Click Install]

== Void Linux ==

Void Linux is another rolling release distribution, utilizing its own package manager.
The current version is available for x86, x86_64, armv6, and armv7.

To install simply run:
<code>xbps-install -S wesnoth</code>

The build is currently maintained by [mailto:itself@hanspolo.net Phillip Hirsch]

== See Also ==
* [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md Compiling Wesnoth]
* [[Download]]

[[Category:Building and Installing]]

WesnothBinariesLinux

2021-11-09T23:50:34Z

Clavi: /* openSUSE */ consistency

{{Translations}}

<div class="tright"> __TOC__ </div>

Not all distributions carry the latest stable or development releases. If you want to make sure you are running the newest official version of Wesnoth from either branch, either get the sources from the [[Download]] page and [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md compile them yourself] or use the nightly flatpak below.

== Flatpak ==
A nightly flatpak of Wesnoth's development branch is available. Instructions for getting it can be found [https://forums.wesnoth.org/viewtopic.php?f=5&t=47872 here].

A flatpak of the current stable release(1.14) is also available [https://flathub.org/apps/details/org.wesnoth.Wesnoth here].

== Arch Linux ==
* The latest stable version can be installed from the [community] repository: <code>pacman -S wesnoth</code>
* There's a wesnoth-devel package for development releases in [https://aur.archlinux.org/packages/wesnoth-devel/ the AUR].

== Debian ==
* [http://packages.debian.org/wesnoth Official packages] including the development releases. If you want a different version, you need to explicitly request which branch you want, e.g. [http://packages.debian.org/wesnoth-1.12 1.12] (stretch), or [http://packages.debian.org/wesnoth-1.14 1.14] (buster, bullseye, and sid)
* [http://backports-master.debian.org/ backports.debian.org] offers the latest stable wesnoth releases, albeit only backported to stretch at this time. For more info on Debian backports, click [http://wiki.debian.org/Backports here].

===Command-line install===
To install Wesnoth, run the following to pull in everything:
aptitude install wesnoth wesnoth-music

===Compiling===

If you want to run a newer release than the ones provided in the Debian repositories, or an unreleased version from the [[WesnothRepository|Git repository]], you will have to build it from source. See [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md Compiling Wesnoth] for more details.

To install Wesnoth's dependencies if you have Debian's source repositories enabled in your config, you can just use apt's <code>build-dep</code> command with the package that best matches the version you are trying to build:

# Stable version
aptitude build-dep wesnoth
# Development version
aptitude build-dep wesnoth-1.14

'''Note:''' If you have already installed an older version of Wesnoth, you should uninstall it first by running:

# Stable version
aptitude purge wesnoth
# Development version
aptitude purge wesnoth-1.14

Bear in mind that this will '''not''' remove downloaded data or saved games stored in your [[EditingWesnoth#The_user_data_directory|home directory]].

Additionally, build-dep will not install libssl-dev automatically due to a Debian patch to use WolfSSL instead due to a licence incompatibility with OpenSSL, so you will need to install that manually. This will likely be resolved within the next couple of years once OpenSSL 3 comes into use since that version will resolve the license incompatibility.

== Ubuntu ==

[http://apt.ubuntu.com/p/wesnoth Click here] to install the latest version of the <code>wesnoth</code> packaged for your release. Alternatively, search for "wesnoth" in the ''Ubuntu Software Center'' or use following command:

sudo apt-get install wesnoth

===Available Versions===

Different releases of Ubuntu provide different versions of Wesnoth in their repositories. Often, this version will be older than the most current Wesnoth.

{| class="wikitable"
|-
! Release
! Packaged Version
|-
| 20.04 LTS (Focal)
| 1.14.9
|-
| 19.10 (Eoan)
| 1.14.7
|-
| 19.04 (Disco)
| 1.14.6
|-
| 18.10 (Cosmic)
| 1.14.4
|-
| 18.04 LTS (Bionic)
| 1.12.6
|-
| 16.04 LTS (Xenial)
| 1.12.5
|}

== Fedora ==
Battle for Wesnoth is included in [http://koji.fedoraproject.org/koji/packageinfo?packageID=4097 Fedora]. The current version of Battle for Wesnoth is available for ARMv7HL, AArch64, ppc64le, s390x, x86, and x86_64 architectures. If you have problems with these packages, or other questions, please contact the Fedora maintainer [mailto:klember@redhat.com Kalev Lember].

To install from command-line, simply run:
dnf install wesnoth wesnoth-tools wesnoth-server

== Gentoo ==
To install the game only, run the following as root:
emerge wesnoth

To install the game and the server, add 'server' to your USE flags, then run emerge as above.

Note: Gentoo currently operates as a rolling-release, updated approximately weekly.

To install the latest unstable version (when available), add the following line to your /etc/portage/package.keywords file before running the emerge command:

games-strategy/wesnoth ~*

The ebuild is currently maintained by [https://wiki.gentoo.org/wiki/Project:Games the Gentoo Games Project]

== Mageia / Rosa Linux / OpenMandriva Lx ==

To install the latest stable version (as root):

urpmi wesnoth

For the development version (Rosa Linux and OpenMandriva Lx only, as root):

urpmi wesnoth-unstable

You can also use the GUI package manager RPMDrake (in the Control Centre).

To install latest Battle for Wesnoth version available you need to enable the following repository using the Control Centre:

{|align="left" border="1"
!align="left"|Distribution
!align="left"|Repository for wesnoth
!align="left"|Repository for wesnoth-unstable
|-
|Rosa Linux Desktop / OpenMandriva Lx
|contrib release
|contrib updates
|-
|Rosa Linux LTS
|contrib updates
|contrib updates
|-
|Mageia
|core release
|N/A
|}




==openSUSE==

These are builds of The Battle For Wesnoth for several versions of openSUSE, made for both i386 and x86_64 architectures.

The openSUSE packages are maintained by [https://build.opensuse.org/package/view_file/openSUSE:Factory/wesnoth/wesnoth.changes multiple contributors].

===Install using One-Click Installation===

Use the correct link for your version of openSUSE:

* openSUSE Tumbleweed (rolling release) [https://software.opensuse.org/ymp/openSUSE:Factory/standard/wesnoth.ymp One-Click Install]
* openSUSE Leap 15.3 (fixed release) [https://software.opensuse.org/ymp/openSUSE:Backports:SLE-15-SP3/standard/wesnoth.ymp One-Click Install]

== Void Linux ==

Void Linux is another rolling release distribution, utilizing its own package manager.
The current version is available for x86, x86_64, armv6, and armv7.

To install simply run:
<code>xbps-install -S wesnoth</code>

The build is currently maintained by [mailto:itself@hanspolo.net Phillip Hirsch]

== See Also ==
* [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md Compiling Wesnoth]
* [[Download]]

[[Category:Building and Installing]]

WesnothBinariesLinux

2021-11-09T23:49:34Z

Clavi: /* openSUSE */ updated 13 years out of date maintainer info, corrected spelling of "openSUSE", updated links with current distros

{{Translations}}

<div class="tright"> __TOC__ </div>

Not all distributions carry the latest stable or development releases. If you want to make sure you are running the newest official version of Wesnoth from either branch, either get the sources from the [[Download]] page and [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md compile them yourself] or use the nightly flatpak below.

== Flatpak ==
A nightly flatpak of Wesnoth's development branch is available. Instructions for getting it can be found [https://forums.wesnoth.org/viewtopic.php?f=5&t=47872 here].

A flatpak of the current stable release(1.14) is also available [https://flathub.org/apps/details/org.wesnoth.Wesnoth here].

== Arch Linux ==
* The latest stable version can be installed from the [community] repository: <code>pacman -S wesnoth</code>
* There's a wesnoth-devel package for development releases in [https://aur.archlinux.org/packages/wesnoth-devel/ the AUR].

== Debian ==
* [http://packages.debian.org/wesnoth Official packages] including the development releases. If you want a different version, you need to explicitly request which branch you want, e.g. [http://packages.debian.org/wesnoth-1.12 1.12] (stretch), or [http://packages.debian.org/wesnoth-1.14 1.14] (buster, bullseye, and sid)
* [http://backports-master.debian.org/ backports.debian.org] offers the latest stable wesnoth releases, albeit only backported to stretch at this time. For more info on Debian backports, click [http://wiki.debian.org/Backports here].

===Command-line install===
To install Wesnoth, run the following to pull in everything:
aptitude install wesnoth wesnoth-music

===Compiling===

If you want to run a newer release than the ones provided in the Debian repositories, or an unreleased version from the [[WesnothRepository|Git repository]], you will have to build it from source. See [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md Compiling Wesnoth] for more details.

To install Wesnoth's dependencies if you have Debian's source repositories enabled in your config, you can just use apt's <code>build-dep</code> command with the package that best matches the version you are trying to build:

# Stable version
aptitude build-dep wesnoth
# Development version
aptitude build-dep wesnoth-1.14

'''Note:''' If you have already installed an older version of Wesnoth, you should uninstall it first by running:

# Stable version
aptitude purge wesnoth
# Development version
aptitude purge wesnoth-1.14

Bear in mind that this will '''not''' remove downloaded data or saved games stored in your [[EditingWesnoth#The_user_data_directory|home directory]].

Additionally, build-dep will not install libssl-dev automatically due to a Debian patch to use WolfSSL instead due to a licence incompatibility with OpenSSL, so you will need to install that manually. This will likely be resolved within the next couple of years once OpenSSL 3 comes into use since that version will resolve the license incompatibility.

== Ubuntu ==

[http://apt.ubuntu.com/p/wesnoth Click here] to install the latest version of the <code>wesnoth</code> packaged for your release. Alternatively, search for "wesnoth" in the ''Ubuntu Software Center'' or use following command:

sudo apt-get install wesnoth

===Available Versions===

Different releases of Ubuntu provide different versions of Wesnoth in their repositories. Often, this version will be older than the most current Wesnoth.

{| class="wikitable"
|-
! Release
! Packaged Version
|-
| 20.04 LTS (Focal)
| 1.14.9
|-
| 19.10 (Eoan)
| 1.14.7
|-
| 19.04 (Disco)
| 1.14.6
|-
| 18.10 (Cosmic)
| 1.14.4
|-
| 18.04 LTS (Bionic)
| 1.12.6
|-
| 16.04 LTS (Xenial)
| 1.12.5
|}

== Fedora ==
Battle for Wesnoth is included in [http://koji.fedoraproject.org/koji/packageinfo?packageID=4097 Fedora]. The current version of Battle for Wesnoth is available for ARMv7HL, AArch64, ppc64le, s390x, x86, and x86_64 architectures. If you have problems with these packages, or other questions, please contact the Fedora maintainer [mailto:klember@redhat.com Kalev Lember].

To install from command-line, simply run:
dnf install wesnoth wesnoth-tools wesnoth-server

== Gentoo ==
To install the game only, run the following as root:
emerge wesnoth

To install the game and the server, add 'server' to your USE flags, then run emerge as above.

Note: Gentoo currently operates as a rolling-release, updated approximately weekly.

To install the latest unstable version (when available), add the following line to your /etc/portage/package.keywords file before running the emerge command:

games-strategy/wesnoth ~*

The ebuild is currently maintained by [https://wiki.gentoo.org/wiki/Project:Games the Gentoo Games Project]

== Mageia / Rosa Linux / OpenMandriva Lx ==

To install the latest stable version (as root):

urpmi wesnoth

For the development version (Rosa Linux and OpenMandriva Lx only, as root):

urpmi wesnoth-unstable

You can also use the GUI package manager RPMDrake (in the Control Centre).

To install latest Battle for Wesnoth version available you need to enable the following repository using the Control Centre:

{|align="left" border="1"
!align="left"|Distribution
!align="left"|Repository for wesnoth
!align="left"|Repository for wesnoth-unstable
|-
|Rosa Linux Desktop / OpenMandriva Lx
|contrib release
|contrib updates
|-
|Rosa Linux LTS
|contrib updates
|contrib updates
|-
|Mageia
|core release
|N/A
|}




==openSUSE==

These are builds of The Battle For Wesnoth for several versions of openSUSE, made for both i386 and x86_64 architectures.

The openSUSE packages are maintained by [https://build.opensuse.org/package/view_file/openSUSE:Factory/wesnoth/wesnoth.changes multiple contributors].

===Install using One-Click Installation===

Use the correct link for your version of openSUSE:

* openSUSE Tumbleweed (rolling release) [https://software.opensuse.org/ymp/openSUSE:Factory/standard/wesnoth.ymp One-Click-Install]
* openSUSE Leap 15.3 (fixed release) [https://software.opensuse.org/ymp/openSUSE:Backports:SLE-15-SP3/standard/wesnoth.ymp One-Click-Install]

== Void Linux ==

Void Linux is another rolling release distribution, utilizing its own package manager.
The current version is available for x86, x86_64, armv6, and armv7.

To install simply run:
<code>xbps-install -S wesnoth</code>

The build is currently maintained by [mailto:itself@hanspolo.net Phillip Hirsch]

== See Also ==
* [https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md Compiling Wesnoth]
* [[Download]]

[[Category:Building and Installing]]