https://bugzilla.novell.com/show_bug.cgi?id=215649 ------- Comment #27 from marcio.ferreira@gmail.com 2006-11-02 19:44 MST ------- Quick flame (jump this paragraphg if you want). Novell/SUSE/SUSE Labx/ex-SUSE Labs/whatever people (ok, Andreas, not SUSE Labs, as Ive said before, or as Ive seen ted haeger refering to nbg people, or as Ive seen in some greg kreoah presentation) should have the balls to fix this, but Im not sure they will, its all about politics, gnome desktop and enterprise bla bla bla. And distro quality dropping, and opensuse becoming fedora. (In reply to comment #23)
Not to mention that the Automatic Online Update Setup in YaST writes a cron rule which calls rug, and that KDE users who try to set up their systems for automatic updates would not get any security patches because the tool to install them is not even installed at all. And installing it later doesn't help because it's then still unable to install any patches because it has no services.
You are very creative to find ways for not dropping zmd, but Im not so sure if you put that effort generally. Lets see, install the update source via a preinstall script in rug rpm? Makje it add a generic redirector (like software.opensuse.org)? Sure looks like an ugly hack, sure looks like somethintg that will fail a lot. Sure thing its in the average quality of other hacks that are already in the system, including the most official one, called ZMD
I can't believe that we are, less than 4 weeks before the final freeze, again discussing how to break another distribution directly before the release and how to make it basically unsupportable.
Repeating: Ive seen it happenning before, just one release ago.
It's unbelievable and the ignorance of the impact of such a change is shocking. It is still definitely not as easy as removing zmd from a pattern and the impact is still more severe than not >having
I disagree... Ive been running here without zmd for months. All good, all fine. No need for rescue etc etc. And you are preseting scenarios that will solve 0.01% of the users. What about the other 99%? Ive used to think somewhere close to you, but that was before 10.1, when I thought quality for a release of SUSE was absolutely necessary. But now its just a common trade off. No biggie if its released a little bit broken (or a lot bit broken, like 10.1). Therefore, I have no moral problems and I will sleep at night if 10.2 is released very slightly broken (much much less than 10.1).
In order to have a distribution that is supportable without zmd installed by default, _nothing_ in the distribution must assume zmd to be present and everything that does must be changed. Slightly difficult in a feature-frozen distribution, I'd say.
if there´s a will, there´s a way
Guys, you can't change the Automatic Online Setup now to write a zypper cron job because that way you're forcing a basically untested tool upon all users,
Exactly what they did to include zmd in 10.1
and the other way round, you can't release a distribution
right
that writes a cron rule with a tool that is not even installed by default because that's broken.
We have a broken tool installed by default (its not only yast sources that dont get well synced to zmd, the other way zmd->yast is also true, but hey, not your problem, right?). Its called zmd. But the worst part of that is not this fact. The worse part is that we have a system to support something that is not goin to happen, which is connecting to a Zen server.
It is damn late for this change!
if there´s a will, there´s a way
Let's make Zenworks easily unselectable, easily deinstallable, declare this unsupported for now because it is not supportable and then try to work towards a 10.3 distribution that does not only leave zmd out of the default installation, but actually _works_ without it.
Will you support that path? Towards removing zmd? To resume in one phrase all this thing: any change here wont get this shit worse than it already is. Thats the "shocking truth". -- 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.