Handbook Talk:Parts/Portage/Advanced
epatch_user is deprecated
I am not so good with EAPI, but looks like with EAPI 6 epatch_user should be updated with eapply_user. Link. --Cronolio (talk) 21 January 2017 (UTC)
Useless semicolons
Take a look at the following bash code:
/etc/portage/bashrcHooking into the postinst and postrm phases'"`UNIQ--pre-00000000-QINU`"'
We can remove useless semicolons between "then" and "fi":
/etc/portage/bashrcHooking into the postinst and postrm phases'"`UNIQ--pre-00000003-QINU`"'
— The preceding unsigned comment was added by Fturco (talk • contribs) 12:39, May 19, 2017
- Fixed. Thanks, Fturco! --Maffblaster (talk) 20:52, 22 May 2017 (UTC)
Adding relevant hyperlink
This page mentions /etc/portage/bashrc multiple times, but none of these instances link to /etc/portage/bashrc, the page that documents this file. At least the first one in running text should. Median (talk) 16:26, 19 April 2018 (UTC)
Grammar fix
- Note
If a different name would be chosen, then it needs to be a script that calls /usr/bin/eix-update instead. The eix binary looks at how it has been called to determine which function to execute. If a symlink would be created that points to eix yet is not called eix-update, it will not run correctly.
This paragraph makes incorrect use of conditionals.
If a different name is chosen, then it needs to be a script that calls /usr/bin/eix-update instead. The eix binary looks at how it has been called to determine which function to execute. If a symlink were created that pointed to eix yet was not called eix-update, it would not run correctly.
Waldo Lemmer (talk) 03:10, 27 March 2024 (UTC)
- Fixed in Special:Diff/1298197/1298199, thanks!
- --csfore (talk) 20:28, 11 May 2024 (UTC)
Typo fix
which is a symbolic link to the a target profile directory
which is a symbolic link to the target profile directory
Waldo Lemmer (talk) 03:18, 27 March 2024 (UTC)
- Fixed in Special:Diff/1298195/1298197, thanks!
- --csfore (talk) 20:26, 11 May 2024 (UTC)
7 years later, epatch_user is still deprecated
I don't think the Handbook is the right place to talk about legacy tools. I propose the following update to section Applying non-standard patches:
Patching source code using user patches in /etc/portage/patches/
User patches provide a way to apply patches to package source code when sources are extracted before installation. This can be useful for applying upstream patches to unresolved bugs, or simply for local customizations.
Patches need to be dropped into /etc/portage/patches/. They will automatically be applied during package installation.
Patches can be dropped into any of the following directories:
- /etc/portage/patches/${CATEGORY}/${P}/ e.g. /etc/portage/patches/dev-lang/python-3.3.5-r1/
- /etc/portage/patches/${CATEGORY}/${PN}/ e.g. /etc/portage/patches/dev-lang/python-3.4.2/
- /etc/portage/patches/${CATEGORY}/${P}-${PR}/ e.g. /etc/portage/patches/dev-lang/python-3.3.5-r0/
Example: Applying patches to Firefox
If for some reason (for instance because a developer provided a patch and asked to check if it fixes the bug reported) patching Firefox is wanted, all that is needed is to put the patch in /etc/portage/patches/www-client/firefox/ (probably best to use the full name and version so that the patch does not interfere with later versions) and rebuild Firefox.
I would propose further additions to the last section with explanations on creating patch files, but I think that should be a separate discussion.
Waldo Lemmer (talk) 03:58, 27 March 2024 (UTC)
- Fixed in Special:Diff/1271693/1298195, thanks!
- --csfore (talk) 20:24, 11 May 2024 (UTC)