Change description of package.use
I was wondering if it is acceptable to change the description of package.use, since it's a directory and no longer just a file.
- Currently, the text says "To accomplish this, edit /etc/portage/package.use. This is usually a single file, but can also be a directory; see man portage for more information. The following examples assume package.use is a single file.". Is there any particular place that you believe we are in error?
- Or is the suggestion to switch the instructions completely to a directory-based approach, and only mention that it can also just be a single file (i.e. revert the logic)? --SwifT (talk) 11:17, 4 March 2015 (UTC)
- I'm closing this discussion because there really is no problem here. Two years is along enough to have no feedback from this user... one quarter year would be long enough. With that being said, I was seeing our amd64 Minimal LiveCD going out with a single child file in the package.use/ directory. As Sven Vermeulen (SwifT) noted we mention both single-file and directory here, so this discussion is really a non-issue. I'll review the text once more and add a small tip about how to name the new package.use file child file if package.use/ exists as a directory. It should help some newcomers out a bit. --Maffblaster (talk) 17:57, 17 April 2017 (UTC)
"changes in these file will be undone when the Gentoo repository is updated!"
"these file" should be fixed with "these files" (plural version).
USE="-kde -qt4 ldap"
USE="-kde -qt4 -qt5 ldap"
"For instance, to remove support for KDE and QT but add support for ldap, the following USE can be defined in /etc/portage/make.conf"
The proper spelling is Qt, not QT.
- Good suggestion here. It's important to keep up with changing 'global' USE flags. Both are fixed as of right now. Thanks! --Maffblaster (talk) 17:46, 17 April 2017 (UTC)
Remove Qt4 USE flag
USE="-kde -qt4 -qt5 ldap"
USE="-kde -qt5 ldap"
since the Qt4 USE flag no longer exists (since Qt4 has been removed).
Update Examples for Available Packages
I would make this change, if I were permitted so to do. In the section Viewing available USE flags an example is given:
equery --nocolor uses =gnumeric-1.12.31
[ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-office/gnumeric-1.12.31: U I + + introspection : Add support for GObject based introspection - - libgda : Enable database support through gnome-extra/libgda. - - perl : Enable perl plugin loader. + + python : Enable python plugin loader. + + python_targets_python2_7 : Build with Python 2.7
It really ought to look like this, given the current state of the repository:
equery --nocolor uses =gnumeric-1.12.47
[ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-office/gnumeric-1.12.47: U I + - introspection : Add support for GObject based introspection - - libgda : Enable database support through gnome-extra/libgda. - - perl : Enable perl plugin loader. - - python_targets_python3_6 : Build with Python 3.6 + + python_targets_python3_7 : Build with Python 3.7 - - python_targets_python3_8 : Build with Python 3.8