Many of the basic portage configuration files are not installed as default. For example, I needed to test an unstable package and the documentation stated that I should add an entry into /etc/portage/package.keywords. I looked and found this file, as well as others, did not exist in my system. So I ended up reading through three documents and guessed that a stub file was simply not installed as opposed to the documentation being out of sync with the system. Reproducible: Always Steps to Reproduce: 1. install a clean system 2. look for basic configuration files such as those in the portage(5) and ebuild(1) documentation... Actual Results: The basic configuration files (such as package.keywords, package.unmask, etc.) are not installed in the system. Expected Results: basic sub files with some comments on where to find documetation. Since most of the files appear to support comments, I would have expected a package.keywords stub file to look something like: # This file contains per-package KEYWORDS used by the portage system. # These are useful for mixing unstable packages in with a normally # stable machine or vice versa. This will allow you to augment # ACCEPT_KEYWORDS for a single package. Please see the portage(5) man # pages for more detail # Examples (remove first # to uncoment): # # always use unstable libgd # media-libs/libgd ~x86 # # only use stable mplayer # media-video/mplayer -~x86 # # use a package that is marked -* # >=sys-kernel/linux-headers-2.6 -*
*** This bug has been marked as a duplicate of 53196 ***
