On Sunday 20 August 2006 09:03, Marcus Meissner wrote:
On Sat, Aug 19, 2006 at 05:19:27PM -0800, John Andersen wrote:
On Saturday 19 August 2006 14:30, Marcus Meissner wrote:
On Sat, Aug 19, 2006 at 06:13:10PM -0400, suse@rio.vg wrote:
Marcus Meissner wrote:
This has nothing to do with it. The /suse/ is superflous, it will fallback to "old style" packages if not used, which is smaller.
Are you trying to suggest that you didn't design the system so that it downloads large repo-data lists multiple times with no dialog or progress meter whatsoever leaving the user to think the whole thing has simply locked up? That may be fine when you're connected to the repo via lan, but did it ever occur to you that some poor shmuck might be on the other end of a modem on the other side of the planet?
You are using poor rhetorics and blame shifting.
Tell us where the blame belongs and we will focus our attention somewhere other than on you Marcus. ;-)
Your problem is you are conveniently "here".
I am angry the same way you are, being the security guy who has to use this framework :/
The problem is that there is no one good to blame, since all can be explained by rational decisions in the end.
- We needed to change and enhance the package handling. mostly for multiple repositories, the easy ability to have add-on products, integration of the "update" mechanism with the regular package manager.
- We needed to incorporate ZEN to have a concise remote management solution for SLE, our large customers just want this.
It was also an attempt to bring ZEN internally closer to YAST.
It worked to some degree, but there are problems to be worked out.
- Timing :/ We could not delay until it was as (quality) ready as we would have liked it, mostly we could not delay SUSE Linux any longer
Ciao, Marcus
In That case then suse should have been released using the tried and trusted Yast not this hotch potch collection of odes and ends called ZEN or whatever it is is Pete .