[EMAIL PROTECTED] ha scritto:
I noticed the file /var/lib/portage/config and wonder what it is.I bet it's used to see if the config files installed two different emerge are the same, in this way:
I could not find it mentioned in the portage, emerge, or ebuild man
pages. I also looked in the portage chapter of the handbook.
# emerge mysql
install a file in /etc/mysql/my.cnf, portage add an entry to .../config with it md5 sum.
after this you hand modify it
after a while you emerge again mysql
# emerge mysql
portage cannot analyze your /etc/mysql/my.cnf because you'd modified it. But portage is smart
and go to see if the new /etc/mysql/my.cnf is the same it has recorded in .../config.
If not you'll be prompted to keep your system in order with etc-update.
in that file should stay all the files that match CONFIG_PROTECT variable (emerge --info show this one)
It should not to be a disaster delete that file just boring.
Add manually stuff into .../world is not a good idea,I ask because I have a problem with it. For some reason I cannot understand this file was moved (I guess by me) to /local/var/lib/portage/config and presumably a symlink left in /var/lib/portage. However, there is no symlink in /var/lib/portage and a new version of config has been generated.
The same thing occurred with /var/lib/portage/world, but I understand this file and merged the two versions (after checking the new small one for sanity).
Should I also merge the two config files and can I alphabetize them
and uniq the result?
# emerge --noreplace $(cat ../oldworld)
should be better, leave it insert the packages into world,
also *don't* sort it, I bet again that the order of emerge is important, surely it can rebuild it but leave it in it's original sorting IMHO is waaaay more secure.
thanks,
allan
prego Francesco
-- [email protected] mailing list
