summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006761.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006761.html')
-rw-r--r--zarb-ml/mageia-dev/2011-July/006761.html155
1 files changed, 155 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006761.html b/zarb-ml/mageia-dev/2011-July/006761.html
new file mode 100644
index 000000000..f334504d9
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-July/006761.html
@@ -0,0 +1,155 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] kernel 3.0 is a big mistake in cauldron
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20kernel%203.0%20is%20a%20big%20mistake%20in%20cauldron&In-Reply-To=%3C201107161503.48071.anaselli%40linux.it%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="006760.html">
+ <LINK REL="Next" HREF="006765.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] kernel 3.0 is a big mistake in cauldron</H1>
+ <B>Angelo Naselli</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20kernel%203.0%20is%20a%20big%20mistake%20in%20cauldron&In-Reply-To=%3C201107161503.48071.anaselli%40linux.it%3E"
+ TITLE="[Mageia-dev] kernel 3.0 is a big mistake in cauldron">anaselli at linux.it
+ </A><BR>
+ <I>Sat Jul 16 15:03:47 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006760.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron
+</A></li>
+ <LI>Next message: <A HREF="006765.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6761">[ date ]</a>
+ <a href="thread.html#6761">[ thread ]</a>
+ <a href="subject.html#6761">[ subject ]</a>
+ <a href="author.html#6761">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> &quot;THE ONE AND ONLY THING properly designed in Windows is that you can use
+</I>&gt;<i> (almost) ANY version of ANY application w/o breaking the system and w/o
+</I>&gt;<i> upgrading the system!&quot;
+</I>*Almost* as you said. Also windows changed and sometimes changes
+between a sp to another, sometimes (often) some applications
+just stop working.
+And yes you can take the old one. But it's not always easy.
+It depends on the good will of developers, not all the not open source
+projects leave old packages to download...
+And yes, you've probably been right, it's *very* *easy* to downgrade a
+W. service pack...
+
+&gt;<i> In all the Linux distros, once the official repos have upgraded an
+</I>&gt;<i> application, you're normally supposed to use it, because downgrading is:
+</I>&gt;<i> (1) difficult;
+</I>For those who do not want to learn yes. For those who are just users yes.
+The first kind cannot complain, the second one yes. But some distros
+add some package that allows to install new programs locally
+(one of those was called autopackage, now forked... i tested once,
+worked but *I* did not need such a feature).
+&gt;<i> (2) discouraged.
+</I>Why? locally you can always do what you want. I remember a friend that
+installed a RH, but after that he installed all the programs he needs
+by using configure make make install... it was not a red hat anymore
+but it started like it was. He had what he needed and worked how he liked to.
+
+&gt;<i> Because, postulate 2, &quot;whereas different versions of system DLLs can
+</I>&gt;<i> coexist in a given Windows release, this is typically impossible in Linux,
+</I>&gt;<i> BY DESIGN&quot; (and this is not about GTK+1 coexisting with GTK+2, nor about
+</I>&gt;<i> KDE3 compatibility libs in KDE4, and also not about installing in /opt or
+</I>&gt;<i> other tricks).
+</I>different dlls can lay on the system only if the are different. e.g name version
+etc, the same it's for .so files. So the problem is not on the system but on
+the developers, if they break abi and don't change the so version according
+and the packager does not see that, then yes they can't co-exists.
+
+&gt;<i> Breaking a package is one thing, breaking the kernel is a totally different
+</I>&gt;<i> one.
+</I>Why don't you ask that to those people that run to buy windows vista after
+an update of a famous anti-virus in XP, because they cannot use their system
+any more?
+
+
+
+--
+ Angelo
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: This is a digitally signed message part.
+URL: &lt;/pipermail/mageia-dev/attachments/20110716/8d003769/attachment.asc&gt;
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006760.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron
+</A></li>
+ <LI>Next message: <A HREF="006765.html">[Mageia-dev] kernel 3.0 is a big mistake in cauldron
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6761">[ date ]</a>
+ <a href="thread.html#6761">[ thread ]</a>
+ <a href="subject.html#6761">[ subject ]</a>
+ <a href="author.html#6761">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>