I had no idea this existed, since it's not mentioned in the Files/other sections of the man page. Now that I know what it is by asking in the IRC, I noticed it's mentioned in the tbz2file section, but still it passes unnoticed since it's role is ommited.
nor should it be mentioned in `man emerge` ... easy enough to document it in `man portage` though
Ok, makes sense. In that case just remove the mentioned files at man emerge and move them to man portage if not there. And put a notice saying Read the Files of portage. Because this way it leads to believe the only files it uses are the ones listed, that's why I thought (even though it sounded incredible not keeping a readable package list :P) Man emerge should just stick to emerge arguments info and syntax and put a -big- notice to read man portage
the files mentioned at the end of `man emerge` are targeted at configuration settings that'd affect emerge ... /var/db/pkg does not fall into that category
Still, to avoid this confusion it wouldn't hurt to export them to portage in a category "configuration files". Or Saying "these are just the files ment to be edited by the user. To know of more files that affect emerge behaviour, please read portage.
Sorry, actually to be coherent there are files mentioned there that are not supposed to be edited, so should be moved to portage. Therefore with the *warning* I mentioned just now, and the user "supposed to be " edited files, this doc would be perfect, the way I see it :P Still, /var/db/pkg/ /var/cache/edb/ would have to be added to portage
man pages are updated now in svn
Out on 2.1.2.9, thanks
