Difference between pages "Category:FLOP" and "Portage Profile Logic"

(Difference between pages)
(How To Add a FLOP)
 
 
Line 1: Line 1:
This page lists all FLOPs, also known as Funtoo Linux Optimization Proposals. FLOPs are proposals created by our community that describe ways that Funtoo Linux can be improved. You are welcome to submit a FLOP on the wiki for any initiative you have that you think may improve Funtoo Linux. Use FLOPs for things that aren't bugs or small fixes, but for larger initiatives that will make Funtoo Linux better.
+
== Gentoo Initialization ==
== How To Add a FLOP ==
+
To create a new FLOP, enter the name of your FLOP in the field below and click "Create or Edit". You will then be prompted to fill out a form for the FLOP, and enter wikitext on the bottom. When saved, your FLOP will have the prefix "FLOP:" to clearly designate it as a FLOP, so it's not necessary to include phrases like "Funtoo Linux" or "Proposal" in your FLOP name.
+
{{#forminput:form=FLOP|query string=namespace=FLOP}}
+
  
 +
Gentoo profile initialization has been documented in [https://github.com/funtoo/portage-funtoo/commit/4c6826a0029c3c8f0aa92e70b4e50f2ffc58c7fa#diff-0 this GitHub commit], and describes how Gentoo's Portage finds and processes profiles. Funtoo Linux will be making some changes to this algorithm, but first things first -- document the existing functionality. Basically, Gentoo's Portage looks for profiles using this algorithm:
  
This category uses the form [[Has default form::FLOP]].
+
# Does <tt>/etc/make.profile</tt> exist? If so, it defines the primary profile.
[[Category:Internals]]
+
# If not, does <tt>/etc/portage/make.profile</tt> exist? If so, it defines the primary profile.
 +
# Recursively process the <tt>parent</tt> file found in the primary profile to build a list of all cascading profiles
 +
# if <tt>/etc/portage/profile</tt> exists, it is a user-defined profile - tack it to the end of our profile list so it can modify anything in the cascading profiles.
 +
 
 +
Here is a more detailed description of the steps:
 +
 
 +
# Look for a profile directory/symlink at <tt>/etc/make.profile</tt>, if one exists, use this as the main profile directory.
 +
# If <tt>/etc/make.profile</tt> doesn't exist, use <tt>/etc/portage/make.profile</tt> as a back-up location if it exists.
 +
# If neither location exists, then a main profile directory doesn't exist and is undefined (None)
 +
 
 +
Using the main profile directory/symlink found above, the <tt>LocationsManager._addProfile()</tt> recursive function will be called that will create a list of all cascading profiles. This works by looking for a <tt>parent</tt> file in the profile directory. If this file exists, then each line is treated as a ''relative path'' and used to modify the path to the current profile, pointing to a "parent" profile that this particular profile modifies. There can be more than one parent, one per line. ''The first line in the <tt>parent</tt> file is the highest-priority parent.''
 +
 
 +
Once this list is created, the code checks to see if <tt>/etc/portage/profile</tt> directory exists. If it does, it is tacked at the end of the cascading profile list, meaning that it is evaluated last and this user-defined profile has the ability to modify any of the cascading profile settings. It provides an ideal hook point for a user-defined profile that can tweak anything the user wants to modify in the profile.
 +
 
 +
[[Category:Portage]]

Revision as of 18:32, January 21, 2011

Gentoo Initialization

Gentoo profile initialization has been documented in this GitHub commit, and describes how Gentoo's Portage finds and processes profiles. Funtoo Linux will be making some changes to this algorithm, but first things first -- document the existing functionality. Basically, Gentoo's Portage looks for profiles using this algorithm:

  1. Does /etc/make.profile exist? If so, it defines the primary profile.
  2. If not, does /etc/portage/make.profile exist? If so, it defines the primary profile.
  3. Recursively process the parent file found in the primary profile to build a list of all cascading profiles
  4. if /etc/portage/profile exists, it is a user-defined profile - tack it to the end of our profile list so it can modify anything in the cascading profiles.

Here is a more detailed description of the steps:

  1. Look for a profile directory/symlink at /etc/make.profile, if one exists, use this as the main profile directory.
  2. If /etc/make.profile doesn't exist, use /etc/portage/make.profile as a back-up location if it exists.
  3. If neither location exists, then a main profile directory doesn't exist and is undefined (None)

Using the main profile directory/symlink found above, the LocationsManager._addProfile() recursive function will be called that will create a list of all cascading profiles. This works by looking for a parent file in the profile directory. If this file exists, then each line is treated as a relative path and used to modify the path to the current profile, pointing to a "parent" profile that this particular profile modifies. There can be more than one parent, one per line. The first line in the parent file is the highest-priority parent.

Once this list is created, the code checks to see if /etc/portage/profile directory exists. If it does, it is tacked at the end of the cascading profile list, meaning that it is evaluated last and this user-defined profile has the ability to modify any of the cascading profile settings. It provides an ideal hook point for a user-defined profile that can tweak anything the user wants to modify in the profile.