https://bugzilla.novell.com/show_bug.cgi?id=215649 ------- Comment #11 from benji.weber@gmail.com 2006-10-28 10:00 MST ------- Smart is not a solution. Smart has its own set of problems. - Several bugs that affect SUSE more than other distros, including questionable choices for package updates on multilib systems. - It is far slower than YaST/zypper (in 10.2 state) at doing anything intensive, like adding a large rpm-md source, or performing an upgrade calculation on more than a few dozen packages. - Having unofficial repositories of variable package quality preloaded causes problems where users are guaranteed to break their systems by continuously updating to new untested packages. We see this every day in #suse, people smart upgrade to latest kde buildservice repository (which is frequently broken) thinking the update is required and then complain it's not working. - Smart's current interfaces are very unuserfriendly, both the existing CLI and GUI frontends are have numerous inconsistencies. YaST needs considerable work in this area too but smart is a step backwards. - Smart does not give any of the suse specific advantages zypp gives us. - Smart does not support deltarpms, without which dialup users would have to install updates factors of 10 larger than currently. - Smart doesn't support SUSE's patterns, making installing things like "all of kde" or "compiler environment" difficult. - Smart is written in python, and I think integrating with yast would be just as non-trivial as the integration of the mono based zmd etc which is causing us nearly all the problems we have in 10.1 In summary I concur that package management is important and we want the best, but smart is not a solution. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.