Mailinglist Archive: opensuse-project (169 mails)
| < Previous | Next > |
[opensuse-project] opensuse upgrade: newer, faster, worse
- From: Maciej Pilichowski <macias@xxxxxxxxxxxxxxxx>
- Date: Fri, 12 Oct 2007 16:46:51 +0200
- Message-id: <200710121646.51199.macias@xxxxxxxxxxxxxxxx>
Hello,
The reason for this mail is quite simple -- I've been using
open/suse for a long time and I am afraid to see how opensuse is
getting better, yet on the other hand is getting worse.
Better -- because for example computer boots faster, worse --
because to do the same thing as before, user has to download extra
packages, download "outdated" packages or learn again how to make
things work with new tools.
For me meaning of upgrade is simply -- user should upgrade system
and everything should work as before, minimum. The only changes could
be: everything is faster, more secure, reliable, etc.
Examples: opensuse dropped smbfs package some time ago, and this
done silently, when you try to use smbfs... nothing, no information
why, what should user do. losetup worked perfectly well in 10.2,
after upgrade user is supposed to set from scratch her/his
configuration to make things work.
I don't want only to complain, because it is wasting time. My
propositions:
a) let's say user works with OS X.Y with package P installed older
than the basic package from this OS version (example opensuse 10.2
and cups 1.1) -- do not touch such packages! it is clear that user
intentionally downgraded this package to work with it, it was her/his
will so do not force upgrade of such packages
b) dropping software (like smbfs (*)) -- provide fake packages (I
already reported this idea), so when user tries to use it explain
what she/he should do with it
b.1) however this example (*) shows a bad judgement -- I think it is
better to provide unmaintained code to help users, than to remove
such software and make things worse for users (cifs does not work so
well)
c) if one tool is replaced with another (losetup example) provide
converter, so user could call losetup-backward-compability script and
all arguments would be translated to the new tool used in opensuse
d) if it is only possible (technically) maintain backward
compatibility, ignoring current userbase in such manner reminds me of
one big firm and its attitude -- it is bad example to follow
In general: it is better to make things work in one place (opensuse
distribution) so every user could benefit from it, than ignoring
users workplace and making them fix system after upgrade to the state
before upgrade. This just a wasting time.
Backward compatibility really matters -- it is no use I get new, great
cups if it does not work for me at all. The same goes for every other
package. Currently this issue is being treated too lightly (in my
opinion).
Thank you for your time,
have a nice day, bye
--
Maciej Pilichowski
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
The reason for this mail is quite simple -- I've been using
open/suse for a long time and I am afraid to see how opensuse is
getting better, yet on the other hand is getting worse.
Better -- because for example computer boots faster, worse --
because to do the same thing as before, user has to download extra
packages, download "outdated" packages or learn again how to make
things work with new tools.
For me meaning of upgrade is simply -- user should upgrade system
and everything should work as before, minimum. The only changes could
be: everything is faster, more secure, reliable, etc.
Examples: opensuse dropped smbfs package some time ago, and this
done silently, when you try to use smbfs... nothing, no information
why, what should user do. losetup worked perfectly well in 10.2,
after upgrade user is supposed to set from scratch her/his
configuration to make things work.
I don't want only to complain, because it is wasting time. My
propositions:
a) let's say user works with OS X.Y with package P installed older
than the basic package from this OS version (example opensuse 10.2
and cups 1.1) -- do not touch such packages! it is clear that user
intentionally downgraded this package to work with it, it was her/his
will so do not force upgrade of such packages
b) dropping software (like smbfs (*)) -- provide fake packages (I
already reported this idea), so when user tries to use it explain
what she/he should do with it
b.1) however this example (*) shows a bad judgement -- I think it is
better to provide unmaintained code to help users, than to remove
such software and make things worse for users (cifs does not work so
well)
c) if one tool is replaced with another (losetup example) provide
converter, so user could call losetup-backward-compability script and
all arguments would be translated to the new tool used in opensuse
d) if it is only possible (technically) maintain backward
compatibility, ignoring current userbase in such manner reminds me of
one big firm and its attitude -- it is bad example to follow
In general: it is better to make things work in one place (opensuse
distribution) so every user could benefit from it, than ignoring
users workplace and making them fix system after upgrade to the state
before upgrade. This just a wasting time.
Backward compatibility really matters -- it is no use I get new, great
cups if it does not work for me at all. The same goes for every other
package. Currently this issue is being treated too lightly (in my
opinion).
Thank you for your time,
have a nice day, bye
--
Maciej Pilichowski
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |