On 4/10/06, Daevid Vincent <[EMAIL PROTECTED]> wrote: > Richard, once again I thank you for your knowledge. > > > Maybe a ~x86 system just isn't for you.... > > I didn't realize ~x86 was going to be such a headache. When I first > installed gentoo, I read a lot of debates on the list and most people said > that ~x86 was fairly "stable". Plus it seems there is such a LONG lag before > things are marked as stable. Plus for a while (again, this is going on two > years ago now I've had this notebook setup) many of the packages didn't have > "stable" ebuilds, or worse, they were marked stable, but a dependency > package was ~x86 so you had to edit package.keywords and add them...
Well I think ~x86 is generally usable, but you do have to be a bit more cautious. For example, I don't mind --sync every day, but I tend to delay any updates that involve portage, baselayout, or other lowlevel system packages until Friday nights, after making a backup, so I have the whole weekend to pickup the pieces if something should break. And today I think if you encounter anything stable that depends on a ~x86 package, it is a bug, and should be filed as such. > > My file is empty?! :( > > Is there a way to rebuild this file? The job of depscan.sh is to rebuild this file. But if the file exists and is newer than the configuration in /etc, it will not do anything, even it if deptree is empty. So delete deptree, and run depscan.sh again with the --debug option. You should see a bit more happen. > How did this happen? A badly timed Ctrl-alt-del or reboot could be the culprit. There is a window of opportunity while depscan is running that if it is aborted, will leave you with an empty file. -Richard -- gentoo-user@gentoo.org mailing list
