Hi
Assembling a guide of recommended update usage seems like a good idea.
Unfortunately I don't have much time (or much knowledge) on the
matter, and submitting the cluster setup as docs and ebuild has
higher priority (which doesn't mean I have much time for that
either).
Do you know if there
If ever there was a frequently asked question, it's this, or the general
family of what's the best way to do an update in this situation?, like:
What is a recommended way to update an old system to minimize
the amount of broken ebuilds?
What's the best way to do an
On Saturday 12 Nov 2005 8:52 am, Bob Sanders wrote:
emerge sync once per week and let it run over the weekend doing updates.
About once per year -
- emerge sync
- ufed and check out the USE flags. Some changes occur and
they need a
Hi folks
I recently went through the (minor hell) of updating my old workhorse
gentoo box. I hadn't touched the system much (apart from open
services like ssh) for about 1.5 years due to a series of facts:
1) It just worked so darned nice.
2) My phd endstretch didn't leave much time to computer
On Fri, 11 Nov 2005 16:46:41 +0100
Jimmy Rosen [EMAIL PROTECTED] wrote:
Primary:
What is a recommended way to update an old system to minimize the
amount of broken ebuilds?
Is emerge --emptytree world a good idea? Is it better than a clean
install? Or is the documentation's way good
5 matches
Mail list logo
