Difference between revisions of "Localpatch"
m (typos) |
|||
| Line 1: | Line 1: | ||
{{Template:Fancynote|This is just workprint. Feel free to contribute.}} | {{Template:Fancynote|This is just workprint. Feel free to contribute.}} | ||
| + | {{fancyimportant|'''Localpatch feature is severely outdated and removed from portage, use foobashrc ebuild'''!}} | ||
== Installation == | == Installation == | ||
Revision as of 00:43, 3 January 2013
This is just workprint. Feel free to contribute.
Localpatch feature is severely outdated and removed from portage, use foobashrc ebuild!
Installation
localpatch is no longer part of portage. You need to install foobashrc:
# emerge app-portage/foobashrc
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 Hooking In the Emerge Process (Gentoo Manual)). If you do not have your own bashrc yet, you can just link it to foobashrc.bashrc:
# ln -s /etc/portage/foobashrc.bashrc /etc/portage/bashrc
To complete the installation you need to add
foobashrc_modules = "localpatch"
to your make.conf. By un-/commenting this line you can easily activate/deactivate localepatch.
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 make.conf.
The actual patches for a package are placed in subdirectories with one of the following naming shemata:
- ${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 shema are used and are applied within numerical order.
See Also
Localpatch_(Tutorial)
http://forums.funtoo.org/viewtopic.php?id=193
