Randall R Schulz wrote:
On Tuesday 30 October 2007 19:33, Ben Kevan wrote:
Well, they (Novell / SUSE) will get complaints, reports of malfunctions, or people throwing up their hands and walking away (without even bothering to let the vendor know).
It's the principal of least surprise. As it stands, errors are precluded at the expense of start-up time. It's a defensible position. I don't understand this. What will there be to complain about? The source shouldn't be upgraded by design.
I'm simply taking Novell (via you) at your collective words that sometimes the Main Repositories are changed. If that's true, then to disable automatic refresh leaves open the possibility of an error during certain package management operations. At least it did in 10.0. I haven't yet seen it happen on 10.3, but I just today turnd off automatic refresh on the two Main Repositories defined in my package management configuration.
I've done the same. Autorefresh bothers me even for changing repos, not because of the check-if-changed overhead (it's not that much), but because of the time you have to wait until the repo refreshes if changed even if i intend only to search for some package or so. Simply put, with autorefresh, the refreshing hits you quite unexpectedly. With autorefresh off, you always have the possibility to refresh manually whenever you want, or if a problem with the repo occurs (e.g. rpm file not found when trying to install). Jano -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org