Difference between pages "How to Dev" and "Install/Stage3/pt-br"

(Difference between pages)
(How to Develop -- The Quick Summary)
 
m (Tocadotux moved page Install/Stage3/es to Install/pt-br/Stage3/: Change of directory)
 
Line 1: Line 1:
= How to 'dev' =
+
=== Instalndo o Stage 3 tarball ===
__NOTITLE__
+
  
{{fancytip|This page will continue to be updated with development-related information... thanks for your interest :)}}
+
Depois de criar os  filesystems, o próximo passo é baixar o Stage 3 tarball inicial. O Stage 3 é um sistema pré-compiled utilizado como um ponto inicial para instalar o Funtoo Linux. Carregue um dos seguintes URLs em outra janela do navegador:
  
This page serves as the official introduction on how to collaborate with our community and help to improve Funtoo Linux.
+
{{MirrorList}}
  
== Introduction ==
+
Agora, vamos navegar pelos diretórios nos mirrors para encontrar o build apropriado do  Funtoo Linux para você.
  
Thanks for your interest in helping out with Funtoo Linux! Funtoo Linux has existed for several years, and we've been using git since the beginning of the project, but have played with various approaches on how to develop Funtoo Linux in a collaborative fashion. Some approaches have worked, some haven't, and I (Daniel) and others like to periodically experiment with different approaches, so these methods are likely to change in the future.
+
==== Qual Build? ====
  
== How to Develop -- The Quick Summary ==
+
'''Se não estiver certo, escolha <code>funtoo-current</code>.'''
  
Okay, so you want to get involved. How do you do it? Well, here's how we want you to start:
+
Funtoo Linux possui vários 'builds' diferentes, ou variantes. Here is a list of the various builds that are available, and what their distinctive features are:
  
* First, you need to actually ''use'' Funtoo Linux in some capacity.
+
{{TableStart}}
* {{CreateAccount}}
+
<tr><th class="info">Build</th><th class="info">Description</th></tr>
* Help in the [http://forums.funtoo.org forums].
+
<tr><td><code>funtoo-current</code></td><td>The most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.</td></tr>
* Find things that need fixing on [https://bugs.funtoo.org the bug tracker], and submit fixes for them.
+
<tr><td><code>funtoo-current-hardened</code></td><td>Same package set as <code>funtoo-current</code>, but with a hardened, exploit-resistant toolchain.</td></tr>
* If you have a new ebuild, then create an issue on [https://bugs.funtoo.org the bug tracker] for it.
+
<tr><td><code>funtoo-stable</code></td><td>Emphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.</td></tr>
* Testing things and finding bugs is also a form of help.
+
{{TableEnd}}
* Help us document stuff on the wiki. See [[Help:Funtoo Editing Guidelines|How to 'wiki']].
+
* Hang out in <tt>#funtoo</tt> on freenode and chat with us.
+
* Learn more about ebuilds by reading our [[Developer Guide]]. Ask questions.
+
* [[Compare Forked Packages To Gentoo]], find one that needs updating, and ask us how to help.
+
  
If you start doing a good amount of this, you will get noticed and plugged in to our development efforts in a short amount of time.
+
If you want to read more about this, have a look at [[Funtoo_Linux#What_are_the_differences_between_.27stable.27.2C_.27current.27_and_.27experimental.27_.3F|Differences between stable, current and experimental]].
  
Now that you have the big picture, let's start by doing a quick overview of Funtoo infrastructure and how it (currently) relates to Funtoo Linux development.
+
==== What Architecture?  ====
  
== bugs.funtoo.org ==
+
'''If you're not sure, pick <code>x86-64bit</code>, or possibly <code>pure64</code> for server systems.'''
  
Currently, [https://bugs.funtoo.org bugs.funtoo.org] serves as the center of operations for all development. If you're going to collaborate with us, then you should definitely {{CreateAccount}} and familiarize yourself with our bug tracker. We try to ensure that ''all'' work in Funtoo Linux has a corresponding issue opened on the bug tracker, so there is some reference for someone to look to find out ''why'' some change was made.
+
For PC-compatible systems, the following choices are available:
  
== The Wiki ==
+
{{TableStart}}
 +
<tr><th class="info">Architecture</th><th class="info">Description</th></tr>
 +
<tr><td><code>x86-64bit</code></td><td>For modern 64-bit processors. Uses new 64-bit instructions and address space. Maintains 32-bit compatibility with multilib.</td></tr>
 +
<tr><td><code>pure64</code></td><td>For modern 64-bit processors but with no support for 32-bit compatibility.</td></tr>
 +
<tr><td><code>x86-32bit</code></td><td>For older 32-bit systems such as Athlon XP, Pentium 4, or earlier Atom.</td></tr>
 +
{{TableEnd}}
  
You are currently reading the wiki, and it is becoming a more and more important part of development. We currently have the ability to define wiki pages for [[:Category:Ebuilds|Ebuilds]], which are used as official documentation for the ebuild. Documentation is a very important part of Funtoo Linux development, and you're strongly encouraged to read about [[Adding an Ebuild to the Wiki]]. Developers who write good documentation gain much respect :)
+
==== Your SubArch ====
  
== git.funtoo.org ==
+
Inside <code>/funtoo-current/x86-64bit/</code> on one of our mirrors, you'll see a bunch of directories for various ''subarches'' of Funtoo Linux. Subarches are builds of Funtoo Linux that are designed to run on a particular type of CPU, to offer the best possible performance. They also take advantage of the instruction sets available for each CPU.  
  
All of our master git repositories exist on [http://git.funtoo.org git.funtoo.org].
+
If you are using an AMD-based CPU, download a stage3 from <code>generic_64</code>, <code>amd64-k8</code>, <code>amd64-k10</code>, <code>amd64-bulldozer</code>, <code>amd64-piledriver</code>, <code>amd64-steamroller</code> or <code>amd64-jaguar</code>. See [[Subarches#64-bit AMD Processors|our list of 64-bit AMD subarches]] for help figuring out which one is best for you.
  
== GitHub ==
+
If you are using an Intel-based CPU, download a stage3 from <code>generic_64</code>, <code>atom_64</code>, <code>core2_64</code> or <code>corei7</code>. Note that <code>corei7</code> is ideal for any modern Intel processor, including Core i3 and Core i5, and many Xeons.  [[Subarches#64-bit Intel Processors|our list of 64-bit Intel subarches]] for help figuring out which one is best for you.
  
We have mirrors of all our git repositories on [http://github.com/funtoo GitHub]. When we push to a repository on git.funtoo.org, it automatically pushes the change to the corresponding repo on GitHub, too.
+
If you are using a 32-bit CPU, download a stage3 from <code>generic_32</code>, <code>i686</code>, <code>core2_32</code>, <code>atom_32</code> or <code>athlon-xp</code>.
  
This has historically created some confusion, because we don't really (right now) do active development on GitHub, using pull requests. If you have an improvement to Funtoo Linux, we want you to open a bug on our [https://bugs.funtoo.org bug tracker]. However, I am hoping that this will change - see {{Bug|FL-1322}}. But for now, if you create an issue or a pull request on GitHub, we probably won't see it in a timely manner.
+
==== Setting the Date ====
  
== The Git Repositories Themselves ==
+
{{fancyimportant|If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date. However, if you system time is relatively close to correct, you can probably skip this step for now.}}
  
One important thing to understand about Funtoo Linux is that the git tree you receive when you type <tt>emerge --sync</tt> is what I call a ''transport tree'' -- it is used to deliver updates to you, but it is not used for development. Our main <tt>/usr/portage</tt> tree can be seen at http://git.funtoo.org/ports-2012/tree or http://github.com/funtoo/ports-2012 is generated using automated scripts which take the Gentoo Portage tree, various funtoo overlays, and several other overlays and combine them into a unified tree. We generate an updated commit for our transport tree every 4 hours.
+
Now is a good time to verify the date and time are correctly set to UTC. Use the <code>date</code> command to verify the date and time:
  
=== Development Trees ===
+
<console>
 +
# ##i##date
 +
Fri Jul 15 19:47:18 UTC 2011
 +
</console>
  
The repositories that we actually do development in are:
+
If the date and/or time need to be corrected, do so using <code>date MMDDhhmmYYYY</code>, keeping in mind <code>hhmm</code> are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:
  
{{#ask:[[Category:Repositories]] [[Repository Type::Development Tree]]
+
<console>
|? Repository ID}}
+
# ##i##date 071620002011
 +
Fri Jul 16 20:00:00 UTC 2011
 +
</console>
  
[[Repository:Funtoo Overlay|funtoo-overlay]] is where nearly all of the core Funtoo forked ebuilds live. This tree is maintained by senior Funtoo staff and the BDFL, and also contains stuff like our [[Funtoo 1.0 Profile]] system, and the actual scripts that are used to generate our main "transport" tree that users receive.
+
Uma vez que você tenha definido o sistema de horário (system clock), é uma boa ideia copiar o horário para o sistema de horas do seu hardware (hardware clock), assim ele persiste nos reboots:
  
[[Repository:Funtoo LDAP Overlay|The Funtoo LDAP]] and [[Repository:Funtoo GNOME Overlay|GNOME]] overlays are examples of development trees where Funtoo staff have collected a bunch of ebuilds that were cluttering up funtoo-overlay, and placed them in their own repository to improve organization. These are treated as extensions of funtoo-overlay.
+
<console>
 +
# ##i##hwclock --systohc
 +
</console>
  
[[Repository:Funtoo Plex Overlay|The Plex overlay]] and [[Repository:Funtoo DeaDBeeF Overlay|DeaDBeeF]] overlays are examples of overlays that are maintained by independent developers, and these overlays are hosted in these developers' GitHub accounts. We have added these overlays to our merge script, so any updates made to these GitHub repositories are automatically pulled into our transport tree.
+
==== Baixe o Stage3 ====
 +
Uma vez que você está no root filesystem do seu Funtoo Linux, utilize <code>wget</code> para baixar o Stage 3 tarball que você escolheu utilizar como base para o seu novo sistema Funtoo Linux. Ele deve se salvo no direorio <code>/mnt/funtoo</code> como a seguir:
  
So as you can see, there is quite a bit of flexiblity in how updates can be added to our tree. Senior staff can work on the funtoo-overlay, others can work on the more independent GNOME and LDAP overlays, and (mostly) independent developers can happily maintain ebuilds in their own independent overlays, hosted on GitHub.
+
<console># ##i##cd /mnt/funtoo
 +
# ##i##wget http://build.funtoo.org/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz
 +
</console>
 +
 
 +
Note que sistemas 64-bit pode rodar stages 32-bit ou 64-bit, mas o sistema 32-bit podem somente rodar stages de 32-bit. Certifique-se de selecionar um Stage 3 que é apropriado para o seu CPU (processador). Se não estiver certo, é uma aposta segura escolher o stage <code>generic_64</code> ou <code>generic_32</code>. Consulte a página de [[Download]] para mais informações.
 +
 
 +
Uma vez o stage for baixado, extraia os conteúdos com o seguinte comand, substituindo o nome nome real pelo seu stage 3 tarball:
 +
<console>
 +
# ##i##tar xpf stage3-latest.tar.xz
 +
</console>
 +
 
 +
{{important|é muito importante utilizar <code>tar's</code> "<code>'''p'''</code>" option when extracting the Stage 3 tarball - it tells <code>tar</code> to ''preserve'' any permissions and ownership that exist within the archive. Without this option, your Funtoo Linux filesystem permissions will be incorrect.}}

Revision as of 18:51, December 13, 2014

Instalndo o Stage 3 tarball

Depois de criar os filesystems, o próximo passo é baixar o Stage 3 tarball inicial. O Stage 3 é um sistema pré-compiled utilizado como um ponto inicial para instalar o Funtoo Linux. Carregue um dos seguintes URLs em outra janela do navegador:

Agora, vamos navegar pelos diretórios nos mirrors para encontrar o build apropriado do Funtoo Linux para você.

Qual Build?

Se não estiver certo, escolha funtoo-current.

Funtoo Linux possui vários 'builds' diferentes, ou variantes. Here is a list of the various builds that are available, and what their distinctive features are:

BuildDescription
funtoo-currentThe most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.
funtoo-current-hardenedSame package set as funtoo-current, but with a hardened, exploit-resistant toolchain.
funtoo-stableEmphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.

If you want to read more about this, have a look at Differences between stable, current and experimental.

What Architecture?

If you're not sure, pick x86-64bit, or possibly pure64 for server systems.

For PC-compatible systems, the following choices are available:

ArchitectureDescription
x86-64bitFor modern 64-bit processors. Uses new 64-bit instructions and address space. Maintains 32-bit compatibility with multilib.
pure64For modern 64-bit processors but with no support for 32-bit compatibility.
x86-32bitFor older 32-bit systems such as Athlon XP, Pentium 4, or earlier Atom.

Your SubArch

Inside /funtoo-current/x86-64bit/ on one of our mirrors, you'll see a bunch of directories for various subarches of Funtoo Linux. Subarches are builds of Funtoo Linux that are designed to run on a particular type of CPU, to offer the best possible performance. They also take advantage of the instruction sets available for each CPU.

If you are using an AMD-based CPU, download a stage3 from generic_64, amd64-k8, amd64-k10, amd64-bulldozer, amd64-piledriver, amd64-steamroller or amd64-jaguar. See our list of 64-bit AMD subarches for help figuring out which one is best for you.

If you are using an Intel-based CPU, download a stage3 from generic_64, atom_64, core2_64 or corei7. Note that corei7 is ideal for any modern Intel processor, including Core i3 and Core i5, and many Xeons. our list of 64-bit Intel subarches for help figuring out which one is best for you.

If you are using a 32-bit CPU, download a stage3 from generic_32, i686, core2_32, atom_32 or athlon-xp.

Setting the Date

Important

If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date. However, if you system time is relatively close to correct, you can probably skip this step for now.

Now is a good time to verify the date and time are correctly set to UTC. Use the date command to verify the date and time:

# date
Fri Jul 15 19:47:18 UTC 2011

If the date and/or time need to be corrected, do so using date MMDDhhmmYYYY, keeping in mind hhmm are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:

# date 071620002011
Fri Jul 16 20:00:00 UTC 2011

Uma vez que você tenha definido o sistema de horário (system clock), é uma boa ideia copiar o horário para o sistema de horas do seu hardware (hardware clock), assim ele persiste nos reboots:

# hwclock --systohc

Baixe o Stage3

Uma vez que você está no root filesystem do seu Funtoo Linux, utilize wget para baixar o Stage 3 tarball que você escolheu utilizar como base para o seu novo sistema Funtoo Linux. Ele deve se salvo no direorio /mnt/funtoo como a seguir:

# cd /mnt/funtoo
# wget http://build.funtoo.org/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz

Note que sistemas 64-bit pode rodar stages 32-bit ou 64-bit, mas o sistema 32-bit podem somente rodar stages de 32-bit. Certifique-se de selecionar um Stage 3 que é apropriado para o seu CPU (processador). Se não estiver certo, é uma aposta segura escolher o stage generic_64 ou generic_32. Consulte a página de Download para mais informações.

Uma vez o stage for baixado, extraia os conteúdos com o seguinte comand, substituindo o nome nome real pelo seu stage 3 tarball:

# tar xpf stage3-latest.tar.xz

Important

é muito importante utilizar tar's "p" option when extracting the Stage 3 tarball - it tells tar to preserve any permissions and ownership that exist within the archive. Without this option, your Funtoo Linux filesystem permissions will be incorrect.