On Fri, 2006-05-26 at 02:40 +0200, Anders Johansson wrote:
On Friday 26 May 2006 00:05, Ken Schneider wrote:
The fact that Zen update is broken is not the issue, the issue is that Zen update was -_not_- tested during beta/RC and there was no contingency to go back to SUSEwatcher in the event that Zen was broken. There is nothing worse than burning your bridges behind you. All they had to do is provide the factory source for update and it would have been known that Zen was not working.
I think you're missing how the new updater works. Factory could have been used to test the updater. The new updater is not relying on a special YOU style repository, it will look at all your installation sources. So you could have tested it
No... I do understand how it works, by combining YOU and other sources into one place and using one daemon to check for updates. But this was -not- checked for functionality before the release of 10.1 and now there are many problems with people using Zen. The biggest being wake up times and resources being utilized by Zen. People new to SUSE are going to spread a -lot- of _BAD_ publicity about 10.1. It is all about perception. Once the bugs are worked out it will be a great program but the bugs should have been worked out before forcing it as the only update program available. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998