Difference between pages "Applying Local Patches to Ebuilds" and "Template:SubarchList"

(Difference between pages)
(See Also)
 
 
Line 1: Line 1:
{{fancynote| This is just workprint. Feel free to contribute.}}
+
<tr><td>[[{{{1}}}|{{{3}}}]]</td><td>{{{4}}}</td><td>{{{5|}}}</td></tr>
{{fancyimportant|'''Localpatch feature is severely outdated and removed from portage, use foobashrc ebuild'''!}}
+
 
+
== Installation ==
+
localpatch is no longer part of portage. You need to install {{Package|app-portage/foobashrc}}:
+
<console># ##i##emerge app-portage/foobashrc</console>
+
This will install the script foobashrc.bashrc at /etc/portage/. It is intended to be used in the emerge process through /etc/portage/bashrc (see [http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=6#doc_chap3 Hooking In the Emerge Process (Gentoo Manual)]). If you do not have your own bashrc yet, you can just link it to foobashrc.bashrc:
+
<console># ##i##ln -s /etc/portage/foobashrc.bashrc /etc/portage/bashrc</console>
+
To complete the installation you need to add
+
 
+
<pre>
+
foobashrc_modules = "localpatch"
+
</pre>
+
to your /etc/make.conf. By un-/commenting this line you can easily activate/deactivate localpatch.
+
 
+
== How it works ==
+
 
+
By default, localpatch will look into /etc/portage/localpatches in order to search for patches. This can be changed by setting LOCALPATCH_OVERLAY variable within /etc/make.conf.
+
 
+
The actual patches for a package are placed in subdirectories with one of the following naming schemata:
+
# ${CATEGORY}/${PN}-${PV}-${PR} - example 'app-foo/bar-1.0-r1'
+
# ${CATEGORY}/${PN}-${PV} - example 'app-foo/bar-1.0'
+
# ${CATEGORY}/${PN} - example 'app-foo/bar'
+
Only the patches within the first matching schema are used and are applied within numerical order.
+
 
+
 
+
[[Category:Projects]]
+
[[Category:Portage]]
+
[[Category:Labs]]
+

Revision as of 10:09, December 20, 2014

<tr><td>[[{{{1}}}|{{{3}}}]]</td><td>{{{4}}}</td><td></td></tr>