Transferir do Git

From mediawiki.org
Jump to navigation Jump to search
This page is a translated version of the page Download from Git and the translation is 44% complete.
Other languages:
Bahasa Indonesia • ‎Bahasa Melayu • ‎Deutsch • ‎English • ‎Esperanto • ‎Napulitano • ‎Nederlands • ‎Scots • ‎Türkçe • ‎asturianu • ‎català • ‎dansk • ‎español • ‎français • ‎galego • ‎interlingua • ‎italiano • ‎lietuvių • ‎magyar • ‎norsk bokmål • ‎occitan • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎sicilianu • ‎suomi • ‎svenska • ‎čeština • ‎Ελληνικά • ‎беларуская (тарашкевіца)‎ • ‎български • ‎русский • ‎українська • ‎العربية • ‎سنڌي • ‎فارسی • ‎हिन्दी • ‎ไทย • ‎中文 • ‎日本語 • ‎한국어

Git é um sistema de controlo de versões distribuído. Este permite-lhe transferir a versão mais recente do código fonte, com todos os ramos e lançamentos etiquetados à sua disposição.

Deveria transferir do Git se for um programador e se pretender submeter correções (patches).

Se não deseja programar, mas só pretende instalar o MediaWiki e as extensões, então transfira as versões de "tarball" estáveis

Consulte Git para mais detalhes, particularmente para contribuir. Em baixo estão algumas instruções rápidas para algumas tarefas comuns.

Pré-requisitos

Antes de poder utilizar o Git tem de o instalar. Há várias formas para o obter, dependendo do seu sistema operativo. Siga Gerrit/Tutorial#Configurar Git, ou utilize o seu motor de pesquisa favorito.

É recomendado que tenha o Composer instalado para descarregar e instalar bibliotecas de terceiros, mas não é obrigatório.

Utilizar o Git para transferir o MediaWiki

Transferência

Pode transferir o núcleo do MediaWiki utilizando o Git, bem como todas as extensões atualmente instaladas no cluster de servidores da Fundação Wikimedia e muitas outras extensões alojadas no Gerrit .

The first step is to clone the MediaWiki core repository. This will take a while.

Transferir para desenvolvimento

The latest development version of MediaWiki is tracked in the 'master' branch.

First make sure that you have created a developer account, so that you have an ssh username.

Then, in a terminal window, enter the following command to clone with your ssh <USERNAME> so that you can submit patches for review:

git clone ssh://<NOME DE UTILIZADOR>@gerrit.wikimedia.org:29418/mediawiki/core.git mediawiki

Isto clona todo o repositório principal do MediaWiki, sincronizado com o ramo principal, numa subdiretoria chamada mediawiki.

To install into 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.

Download a stable branch

If you do not want to develop software patches but want to anonymously clone the stable release branch 1.35, use this command instead:

git clone https://gerrit.wikimedia.org/r/mediawiki/core.git --branch REL1_35 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.

Etiquetas do MediaWiki (versão estável)

Alternatively, specific stable versions of MediaWiki are tracked using 'tags'. These are analogous to the tarball releases. Currently, these are 1.35.0 (stable), 1.31.10 (LTS) and 1.34.4 (legacy).

You can see all available tags with:

git tag -l | sort -V

To use a specific tag, e.g. the latest stable release:

git checkout 1.35.0

Update the Git submodules

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

cd mediawiki
git submodule update --init

Obter bibliotecas externas

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.
  • 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:
    • With your developer account, use this command: git clone ssh://<USERNAME>@gerrit.wikimedia.org:29418/mediawiki/vendor.git
    • For anonymous checkout, use this command: 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.

Manter-se atualizado

If you're using a particular branch or the development version ("master" branch) of MediaWiki, picking up the latest changes is relatively easy. Change into your MediaWiki clone directory and issue this command:

git pull

All of the latest changes for the branch you are using will be applied.

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

After updating/upgrading the code and required libraries you should run the MediaWiki update.php command-line script to update database tables as needed:

php maintenance/update.php

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

Mudar para uma versão diferente

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 <nome do ramo>

ou

git checkout <nome de etiqueta>

The changes will be applied automatically and you will be all set to go.

Utilizar o Git para transferir as extensões do MediaWiki

Lista de extensões no git

Transferir uma extensão

In the next commands, replace <EXT> with the name of the extension you want to download, without spaces. For Extension:TitleKey , it would be TitleKey. (case sensitive!)

Transferir e clonar uma extensão a partir do Git:

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

cd /path/to/extensions
git clone ssh://<USERNAME>@gerrit.wikimedia.org:29418/mediawiki/extensions/<EXT>

For anonymous checkout of the stable branch instead, use these commands:

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

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

https://gerrit.wikimedia.org/g/mediawiki/extensions/<EXT>/+/refs/heads/master

Transferir todas as extensões

If you prefer to have all MediaWiki extensions that are at gerrit.wikimedia.org checked out to your machine, enter the following:

With your developer account, to get the master branch:

git clone ssh://<USERNAME>@gerrit.wikimedia.org:29418/mediawiki/extensions

For anonymous checkout of the stable branch instead, use this command:

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

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

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

At any time, to update all extensions to their latest versions of that branch, enter:

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

To change to a different branch, such as after a new release:

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

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

To track the master branch:

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.

Remover uma extensão

  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/

Utilizar o Git para transferir temas do MediaWiki

Lista de temas no git

O MediaWiki 1.24 e superior não inclui os temas na transferência do Git.

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.

Consulte também