[Mageia-dev] kernel 3.0 is a big mistake in cauldron

Angelo Naselli anaselli at linux.it
Sat Jul 16 15:03:47 CEST 2011


> "THE ONE AND ONLY THING properly designed in Windows is that you can use
> (almost) ANY version of ANY application w/o breaking the system and w/o
> upgrading the system!"
*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...

> In all the Linux distros, once the official repos have upgraded an
> application, you're normally supposed to use it, because downgrading is:
> (1) difficult;
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).
> (2) discouraged.
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.

> Because, postulate 2, "whereas different versions of system DLLs can
> coexist in a given Windows release, this is typically impossible in Linux,
> BY DESIGN" (and this is not about GTK+1 coexisting with GTK+2, nor about
> KDE3 compatibility libs in KDE4, and also not about installing in /opt or
> other tricks).
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.
 
> Breaking a package is one thing, breaking the kernel is a totally different
> one.
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: </pipermail/mageia-dev/attachments/20110716/8d003769/attachment.asc>


More information about the Mageia-dev mailing list