Unmasking packages using portage

http://www.calculate-linux.ru/blogs/en/276/show

Sorry for my English, all the notes about mistakes are welcome.

“Not so far ago I found an interesting feature in portage-2.2. Two wonderful options had been appeared in emerge: --autounmask and --autounmask-write. They allow users not to install additional package app-portage/autounmask saving easy and safe handling with package unmasking.”

I think this should say…

“I recently found an interesting feature in portage-2.2. Two wonderful options have been added to emerge: --autounmask and --autounmask-write. They allow users to install packages that normally would be masked and prevented from being installed. Autounmask makes unmasking packages easy by automatically unmasking the selected package as well as its dependencies.”

““If --autounmask is enabled, changes are written to config files. Of course, respecting CONFIG_PROTECT and --ask. If CONFIG_PROTECT is not empty running etc-update would be reminded for config files updating in /etc/portage/.””

Should say…

“If --autounmask is enabled, changes are written to config files. Of course, it will still be limited by settings in CONFIG_PROTECT and --ask. If CONFIG_PROTECT is not empty, then try running etc-update in the terminal to update config files in /etc/portage/.”

"“Take an attention: we’ve taken no deal with dev-libs/libmowgli, everything was done automatically. We’re remembered to run etc-update. Running.”

“Take note: We have not had to manually deal withdev-libs/libmowgli, everything was done automatically. We should then run etc-update, as shown below.”

““for this method worked properly or you would be informed about absence of file for writing in.””

“for this method to work properly, or else you would be notified about the absence of files that would be written to.”

I wish the guide would talk more about CONFIG_PROTECT and how to edit those changes, or turn it off entirely.