Difference between pages "Talk:How Metro Works" and "Portage Tree"

(Difference between pages)
 
(How the Tree is Built)
 
Line 1: Line 1:
I recommend integrating this content into the [[Metro]] main page. We are missing a basic introduction to Metro there - a defintion of what it is, etc.
+
This page describes the Funtoo Linux distributed Portage tree, which contains all the ebuilds of the Funtoo Linux distribution.  
  
---
+
== Community-Extensible and Distributed ==
  
Basic introduction is not needed, the goal of the article is to dive deeper in the subject and this would add redundancy, those who read the article know what metro is. At worst I will put cross a reference (best practice : do cross references, do not repeat the text between articles). Metro is not a single article, it is a set of several articles (this one, the quick start guide, the data modules, used and whatever else added in the future) grouped with the category "Metro"and this what the [[Metro]] page refers to :)
+
Daniel Robbins has recently added the ability for the Portage tree to be extended and improved by the community. This allows Funtoo Linux users to contribute ebuilds of interest very easily, by simply committing their ebuilds to their own git-based portage repository. Your updated ebuilds are then auto-merged into the mainline Funtoo Portage tree every 12 hours. If you are interested in contributing to the Funtoo Linux Portage tree, please post an email to the [http://groups.google.com/group/funtoo-dev funtoo-dev mailing list] describing your overlay and its contents and we will consider the request.
  
However I agree with you, Metro need a bit more verbosity, I would make the [[Metro]] main page more verbose with a list of several sub pages dedicated to a particular subjects. This page is the common denominator of every other.
+
== Mini-Manifest Tree ==
 +
 
 +
Funtoo Linux provides two Portage tree repositories, available at the following location:
 +
 
 +
* http://github.com/funtoo/ports-2012
 +
 
 +
The first tree is a full Portage tree with full Manifests and ChangeLogs, and includes branches for Funtoo Linux as well as Gentoo Linux. The second tree is a minimized tree that contains only the unified Funtoo Linux Portage tree, all the ebuilds in the first tree, but contains "mini" Manifests (that only contain distfile digests) and has ChangeLogs removed. The first tree is used by Funtoo Linux internallly while the second tree is intended to be used by end-users, since it is much smaller.
 +
 
 +
== How the Tree is Built ==
 +
 
 +
New versions of the Funtoo Linux Portage tree are generated every 12 hours using a special merge script that combines the Gentoo Portage tree with the Funtoo Linux funtoo-overlay as well as other 3rd-party overlays. The overlays currently being merged are:
 +
 
 +
* http://github.com/funtoo/portage (gentoo.org branch)
 +
* http://github.com/funtoo/funtoo-overlay (all ebuilds replacing those in Gentoo, including some eclass and profile patches)
 +
* http://github.com/slashbeast/foo-overlay (all ebuilds being added, with two ebuilds replacing an upstream Gentoo version)
 +
* http://github.com/adessemond/bar-overlay (all ebuilds replacing those in Gentoo)
 +
* http://github.com/funtoo/flora [[Flora]] (all ebuilds being added, with no ebuilds replacing upstream Gentoo versions)
 +
 
 +
This list is likely to expand in the future.
 +
 
 +
The script used to merge the Portage overlays can be viewed here:
 +
 
 +
https://github.com/funtoo/funtoo-overlay/blob/master/funtoo/scripts/merge.py
 +
 
 +
If you are interested in contributing ebuilds to Funtoo Linux, please contact us on the [http://groups.google.com/group/funtoo-dev funtoo-dev mailing list].
 +
 
 +
[[Category:Portage]]
 +
[[Category:Funtoo features]]

Revision as of 07:58, November 18, 2012

This page describes the Funtoo Linux distributed Portage tree, which contains all the ebuilds of the Funtoo Linux distribution.

Community-Extensible and Distributed

Daniel Robbins has recently added the ability for the Portage tree to be extended and improved by the community. This allows Funtoo Linux users to contribute ebuilds of interest very easily, by simply committing their ebuilds to their own git-based portage repository. Your updated ebuilds are then auto-merged into the mainline Funtoo Portage tree every 12 hours. If you are interested in contributing to the Funtoo Linux Portage tree, please post an email to the funtoo-dev mailing list describing your overlay and its contents and we will consider the request.

Mini-Manifest Tree

Funtoo Linux provides two Portage tree repositories, available at the following location:

The first tree is a full Portage tree with full Manifests and ChangeLogs, and includes branches for Funtoo Linux as well as Gentoo Linux. The second tree is a minimized tree that contains only the unified Funtoo Linux Portage tree, all the ebuilds in the first tree, but contains "mini" Manifests (that only contain distfile digests) and has ChangeLogs removed. The first tree is used by Funtoo Linux internallly while the second tree is intended to be used by end-users, since it is much smaller.

How the Tree is Built

New versions of the Funtoo Linux Portage tree are generated every 12 hours using a special merge script that combines the Gentoo Portage tree with the Funtoo Linux funtoo-overlay as well as other 3rd-party overlays. The overlays currently being merged are:

This list is likely to expand in the future.

The script used to merge the Portage overlays can be viewed here:

https://github.com/funtoo/funtoo-overlay/blob/master/funtoo/scripts/merge.py

If you are interested in contributing ebuilds to Funtoo Linux, please contact us on the funtoo-dev mailing list.