Create /etc/portage/package.* folders rather than files

[zero]

I am wondering is it possible to change the way the /etc/portage/package.* files work?
If i want to set some personal *.keywords, *.mask, *.use, *.unmask files so that they
don't get overwritten with a Sabayon update. So rather than having /etc/portage/package.*
files, they would be folders that contain the Sabayon package files and my personal
package files. This is the method i am using now with another Gentoo setup and it works
great for better organizing my personal package files and they don't get overwritten
when i update from the package maintainer that i am using. If this is possible already
with the current Sabayon setup please let me know.

[wolfden]

why would those files get overwritten???

[zero]

why would those files get overwritten???

So you are saying that a Sabayon update will not update/overwrite the
keyword files! If this is the case does that means when a package becomes
stable or is no longer needed to be in .unmask, .mask, .keyword, etc...,
do we get notified and have to edit the file ourselves? Is it not a good
idea to use the folder method so as to give the user the ability to set
his own files, apart from the Sabayon keyword files.

EDIT: Is there any adverse effect if i create the folders myself and put
the keyword files in them?

[wolfden]

It all depends on how you are updating I guess

[zero]

I guess i should just ask a simple question. Do
the files *.unmask, *.mask, *.keyword, etc... EVER
get updated by ANY kind of Sabayon update. I am
not talking about a rev update. I am asking is there
any Sabayon command to update Sabayon settings
files "profiles, keyword files, etc.... If not then how
do the keyword files get updated? Four or five months
from now we may no longer need a specific package
in for example the *.mask file and another package
update requires that masked file. Does Sabayon have
a way of notifying the user base to do some kind of
update so that the keyword files get updated?

I have been using the Evolution Mission tarballs and we
had a similar situation where we could just do a Evo
update and it would update the keyword files. For this
reason we had folders and the users were able to have
their own personal keyword files without them getting
overwritten by the updated project keyword files.

[wolfden]

It works same way as gentoo if that is what your asking. You edit those files yourself.