Fix incorrect category for package
In the example pointing to kde-meta:
It should be https://packages.gentoo.org/packages/kde-apps/kde-meta and not https://packages.gentoo.org/packages/kde-base/kde-meta
A tiny issue, but "This does not mean that re-synchronization of the tree several times in a short time period!" doesn't make sense. Someone should delete the "that". Ptolom (talk) 19:26, 28 June 2016 (UTC)
- That package/application is not referenced anywhere on this page, however it is cited in some non-English versions of the Handbook. - dcljr (talk) 10:19, 13 January 2017 (UTC)
Tiny correction in "Finding installed package documentation"
I just think that the code part beiginning with "ls -l /usr/share/doc/alsa-lib-1.0.14_rc1" must be place between " the USE flags chapter." and "Once the package installed" (one paragraph before). — The preceding unsigned comment was added by Hogren (talk • contribs) 11 February 2017
- I'm trying to see what's wrong with this and it looks okay to me. The command to emerge it is listed directly before the ls -l command. --Maffblaster (talk) 04:51, 21 April 2017 (UTC)
HTTP to HTTPS
Please HTTPS instead of HTTP for the following links:
In section "Finding installed package documentation" I would use the following command instead:
equery files --filter=doc alsa-lib
* Searching for alsa-lib ... * Contents of media-libs/alsa-lib-1.1.3: /usr/share/doc/alsa-lib-1.1.3/ChangeLog.xz /usr/share/doc/alsa-lib-1.1.3/NOTES.xz /usr/share/doc/alsa-lib-1.1.3/TODO.xz /usr/share/doc/alsa-lib-1.1.3/asoundrc.txt.xz
- I think this is simple, non-hackish way to do it. Gets my vote. --Zucca (talk) 13:34, 18 April 2017 (UTC)
"In this case, "free" is mostly defined by the FSF and OSI." Why not adding links to their websites?
"Some softwares are only available for a few architectures."
I'm not a native English speaker, but "softwares" seems horrible to me. It should be simply "software", without the trailing "s".
Link to bugs.gentoo.org
- "If not, please file a bug on Gentoo's bugtracking system."
- "If you believe the package does work file a bug at our Bugzilla website."
- "Ask the architecture porting team to test the package or test it for them and report the findings on our Bugzilla website."
- "Please check Bugzilla if the issue is known and if not, please report it."
- "It might also be beneficial to check Bugzilla to see if the issue is known and if not, report it."
- "Check Bugzilla and see if anyone has reported the problem yet or ask around on #gentoo (IRC)."
For each one of the previous sentences I would add a link to https://bugs.gentoo.org/.
- Too many (redundant) links can be a bad thing. I'll add a few more links. --Maffblaster (talk) 03:29, 21 April 2017 (UTC)
"This does not mean that re-synchronization of the tree several times in a short time period!"
I would fix the previous sentence as follows:
"This does not mean that you can re-synchronize the tree several times in a short time period!"
- Someone else pointed this out above. I have reworded the entire paragraph. Thanks! --Maffblaster (talk) 00:51, 18 April 2017 (UTC)
Incorrect Portage package directory name in "License" section
In this sentence "Running emerge --search package/category will show the package's license." should be category/package
Location of licenses in "Licenses" section seems to be incorrect
It's /usr/portage/licenses/ on my system, not /var/db/repos/gentoo/licenses/ as is explained in this section (I also remember other wiki articles referring to /var/db/repos/gentoo which appears to be /usr/portage on my system, but I can't find any right now). Barteks2x (talk) 00:24, 4 November 2019 (UTC)
- Really it should be "$(portageq get_repo_path / gentoo)/licenses/" but the transition is difficult to explain. Old users will have the old path, new users will have the new path. --Grknight (talk) 13:38, 4 November 2019 (UTC)
I also think it would be good to write up a change somewhere in the Handbook to mention the default directory location changes. I just added Portage#Default_Gentoo_ebuild_repository_location_change. Perhaps we can link to that location... Not sure if the title of the section should be change, though... --Maffblaster (talk) 04:53, 1 November 2021 (UTC)
"emaint --auto sync" in "Updating the system" section
Should the generic command to sync Portage not now be "emaint --auto sync", rather than "emerge --sync", as per Project:Portage/Sync ?