--=-y0m3p36sL6/m8VT0cDSz
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2002-06-18 at 08:19, Robert G. Brown wrote:
> I'll also state unambiguously -- many (most?) of the future users of yum
> will not be able to cope with the stream of messages indicating
> conflicted dependencies on an upgrade. If it ain't automagic for them,
> it's broke. They won't care about who screwed up or why it isn't
> working, they'll just consider the tool broken and will drop it.
This is a valid point, but I will have to disagree with the course of
action. Consider an analogy:
Most websites are written for Internet Explorer, and thus are
effectively broken. Mozilla refuses to display Explorer-specific markup
and will therefore show the page incorrectly. We don't nag Mozilla
developers to "fix" this, but instead bitch at the maintainers of that
website to get off their asses and provide valid webpages.
I don't see why we should act in any way different with yum. If a
package is broken -- it's broken. Moreover, apart from some very few
exceptions, our trees are usually upgradeable with all dependencies
resolving (Bero is a separate [nut]case). If the end-user in question
(meaning you) installs some packages on their own that end up breaking
dependencies either during the installation or during the upgrade, they
are effectively their own angry pinoccio.
Regards,
--=20
0> Konstantin ("Icon") Riabitsev
/ ) Duke University Physics Sysadmin
~ www.phy.duke.edu/~icon/pubkey.asc
--=-y0m3p36sL6/m8VT0cDSz
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEABECAAYFAj0PNmgACgkQlVxa81EWb4j/hwCgzlOLOBqLTc6MpSCW803CLfV+
pmsAniiTCdw1KyTUtwCCkAP8Vf8+FPuH
=u7Uw
-----END PGP SIGNATURE-----
--=-y0m3p36sL6/m8VT0cDSz--
