Am Sonntag, 24. Mai 2009 02:59:43 schrieb maxim.wex...@gmail.com: > I meant I did not want things to get too complicated by adding lots of > packages before I understood the system. > > In my grep of env.d their are only 5 lines _all_CONFIG_PROTECT_MASKs. > None of then lead to /etc/init.d. So why should paludis -u cpufreqd > not also remove the actual executable from the dir? Same with > cpufreqd.conf. That too was left behind after the "uninstall" > > You have '43kdepaths:CONFIG_PROTECT="/usr/share/config" ' Did you > write that one yourself or does paludis to that?
Neither. Ebuilds do that.
> I'd like to understand these things before I get in too deep. What
> *is* the difference between CONFIG_PROTECT and CONFIG_PROTECT_MASK?
> One "protects" while the other "masks". Does the one that "masks"
> "protect" some files and not others?
That should be explained in the portage docs.
> Thanks in advance if you wish to spend more time on something you
> already know.
I must admit I never really cared about that stuff.
Bye...
Dirk
signature.asc
Description: This is a digitally signed message part.
