Download fra Git

Git er distribueret versionskontrolsoftware, der giver brugerne mulighed for at downloade den seneste version af en gren uden at skulle vente på, at nogen kommer forbi og indpakker den. MediaWiki vil frigive hurtigere, og det vil være nemmere for dig at opdatere din installation, rulle en opgradering tilbage, eller [$bugzilla indsende rettelser]. (Husk at officielle stabile udgivelser selvfølgelig altid er mindre risikable.) It allows you to download the very latest version of the source code, with all the branches and tagged releases at your disposal.

You should download from Git if you are a developer and want to submit patches.

If you do not want to develop but only install MediaWiki and extensions, then download stable tarball releases instead.

Se Git for flere detaljer, særligt om bidrag. Nedenfor er hurtige retningslinjer for enkelte almindelige opgaver.

Forudsætninger

Git skal installeres før brug. Der er mange forskellige måder at erhverve Git, afhængigt af dit operativsystem. Tjek [$link git-scm.com] for kildekoden og officielle binære filer. Brug din foretrukne søgemaskine, hvis du vil finde instruktioner for alternative måder at installere Git for dit operativsystem. Follow Gerrit/Tutorial#Set up Git, or use your favorite search engine.

It is recommended that you have Composer installed to download and install third party libraries, but not required.

Brug Git til at hente MediaWiki

Hentning

Du kan i øjeblikket downloade MediaWiki kernen (phase3 på SVN) ved hjælp af Git, såvel som enhver udvidelse der er installeret på Wikimedia-stiftelsens serverklynge. Fra juli 2013 vil alle udvidelser enten være tilgængelige ved brug af Git eller de flytter til alternative version kontrol værter.

Det første skridt er at klone MediaWiki lageret. Dette vil tage lidt tid.

Download for development

Den seneste udviklings-version af MediaWiki spores i 'master'-grenen. Det er, hvad der er lokalt tjekket ud som standard, når du først kloner MediaWiki-lageret. Hvis du har skiftet til en anden gren, men gerne vil skifte tilbage, skriv:

Hvis du har udvikler-adgang (som er nemt at anmode om), så istedet for at klone anonymt med https bør du klone med dit ssh <USERNAME> så du kan indsende ændringer for gennemlæsninger:

Then, in a terminal window, enter the following command to clone the repository:

git clone https://gerrit.wikimedia.org/r/mediawiki/core.git mediawiki

This clones the entire MediaWiki core repository, synced to the master branch, into a sub-directory named mediawiki.

To install into a different directory, change that in the command line (for more info refer to these docs). Once the repository is cloned, you can switch to different branches or tags. The development branch, master, is the cutting-edge, developer version of MediaWiki; you should not use master code for production under any circumstances as it is not considered stable.

• Se seneste kildekode

Download a stable branch

Dette kloner hele MediaWiki-kerne lageret, initially pointed at release branch 1.42, into a sub-directory named $dir.

git clone https://gerrit.wikimedia.org/r/mediawiki/core.git --branch REL1_42 mediawiki

If you have a slow internet connection and want to reduce the number of revisions that are cloned, add --depth=1 to the git clone command.

MediaWiki tags (stabil version)

Alternativt spores særlige stabile versioner af MediaWiki ved brug af 'tags'-mærker. Disse er analoge til tarball-udgivelserne. Currently, these are 1.42.3 (stable), 1.39.10 (LTS) and 1.39.10 (legacy LTS).

You can see all available tags with:

git tag -l | sort -V

Hvis du vil bruge et bestemt 'tag'-mærke:

git checkout 1.42.3

Update the Git submodules

The branches and tags have a bunch of Git submodules in them, for commonly-used extensions and skins and for the vendor/ directory. The master branch does not have these. To update the submodules, run:

cd mediawiki
git submodule update --init --recursive

Fetch external libraries

MediaWiki uses Composer to manage external PHP libraries, all of which end up in the vendor/ directory in your MediaWiki directory.

To install these needed libraries, you have a choice:

• Download and install the composer PHAR, optionally rename the composer.phar file as instructed for your OS, and then run composer update --no-dev from your MediaWiki directory. This is the recommended approach.

• • If the default PHP CLI version does not match the web server's PHP version, specify it with e.g. php7.4 composer.phar update --no-dev.

• Or, if you don't want to use Composer or if you want to use the exact same set of vendor libraries as used on the WMF production cluster, you can instead create a vendor/ directory inside the core folder of your MediaWiki installation:

git clone https://gerrit.wikimedia.org/r/mediawiki/vendor.git

• • Note that if any of your extensions have their own Composer requirements, then you cannot use this option.

Prior to MediaWiki 1.25, external libraries were kept in the core repository, and no package manager was required.

Hold dig opdateret

Hvis du bruger en bestemt gren eller udviklings-versionen af MediaWiki, er hentning af de seneste ændringer virkelig nemt. Skift til dit MediaWiki klon bibliotek og udsted pull kommandoen:

git pull

Alle de seneste ændringer til den gren, du bruger, vil blive anvendt.

The new version of core may require newer versions of extensions and skins, so you must go into each extension and skin directory and update it with a command like git pull --recurse-submodules.

You also need to update vendor/ with any newer versions of required libraries. This often means running the following Composer command, but see #Fetch external libraries above for more details:

composer update --no-dev

Også efter opdatering/opgradering, bør du køre MediaWiki update.php fra kommandolinjen:

php maintenance/run.php update

If you use MediaWiki-Vagrant , it offers a single command, vagrant git-update, that performs all these steps.

Skift til en anden version

Each of our versions are tracked as branches or tags. In order to switch to a different version (for example from the master branch to a different branch or tag), checkout the particular branch or tag you want from within your MediaWiki clone directory:

git checkout <branch_name>

eller

git checkout <tag_name>

Ændringerne vil blive anvendt automatisk, og du vil være klar til at gå.

Brug Git til at hente MediaWiki-udvidelser

List of extensions in git

Hent en udvidelse

EXT skal erstattes med navnet på den udvidelse, du vil downloade, uden mellemrum. For Extension:TitleKey -udvidelsen, ville det være TitleKey.

Download og klon en udvidelse fra Git:

With your developer account, use these commands to get the master branch:

cd /path/to/extensions
git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/<EXT>

To clone and checkout a stable release branch instead, use these commands:

cd /path/to/extensions
git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/<EXT> --branch REL1_42

You can view extension source code in Gerrit's gitiles application, and at the URL:

https://gerrit.wikimedia.org/g/mediawiki/extensions/<EXT>/+/HEAD

Hent alle udvidelser

Hvis du foretrækker at have alle MediaWiki-udvidelser, som er på gerrit.wikimedia.org tjekket ud til din maskine, skal du gøre følgende:

git clone https://gerrit.wikimedia.org/r/mediawiki/extensions

Or, to checkout stable releases branch instead, use this command:

git clone https://gerrit.wikimedia.org/r/mediawiki/extensions --branch REL1_42

After running the git clone command, continue with these commands:

cd /path/to/extensions
git submodule update --init --recursive

For at opdatere udvidelserne til deres nyeste versioner, gør bare dette:

cd /path/to/extensions
git pull
git submodule update --init --recursive

For at ændre til en anden gren, som for eksempel efter en ny udgivelse:

git submodule foreach 'git checkout -b REL1_41 origin/REL1_41 || :'

Remember that you should only use versions of extensions from the same release as that version of MediaWiki and each other.

For spore hovedgrenen:

git submodule foreach 'git checkout -b origin/master || :'

Please note that you should not use master code for production under any circumstances as it is not considered stable.

If you only need a read-only checkout (for instance to grep or analyse all MediaWiki code), you can use the shared MediaWiki checkout on Labs, without downloading anything on your machines.

Remove an extension

1. Remove the "require_once …" or "wfLoadExtension( … )" from LocalSettings.php

1. Remove any line referencing the extension in composer.local.json (usually in the "extra → merge-plugin → include" section)

1. Remove the extension's directory in install-dir/extensions/

Using Git to download MediaWiki skins

List of skins in git

MediaWiki 1.24 and later don't include skins in the Git download.

Follow the exact same procedure as for extensions (described in the previous section), but using skins rather than extensions in all URLs and paths.

Detailed installation instructions are available on each skin's page here on MediaWiki.org, for example see Skin:Vector#Installation. Instructions for all other skins are analogous.

Se også

Appendix

The Revision as of 14:26, 21 March 2019 changed the standard of linking to gerrit.wikimedia.org:

fra:

gerrit.wikimedia.org/r/p/mediawiki

til:

gerrit.wikimedia.org/r/mediawiki