Mail Archives: cygwin/2007/07/14/23:44:35
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Olivier Lefevre on 7/14/2007 9:26 PM:
>> Did you read the announcements/README?
>
> Admittedly no. I updated in a rush after a new antivirus broke my cygwin
> installation and didn't read anything. In any case I don't expect and I
> don't welcome policy changes, esp. such disruptive ones, in a minor
> release.
This behavior has been present in cygwin to some degree since bash 3.2.0,
in October of last year, which was a major version upgrade from bash 3.1.x
(and the change was available in experimental releases before that,
starting with bash 3.1-8 in September), and was based on lots of feedback
from this list. In other words, I did not make the change on a whim in a
minor release, nor did I do it in the dark. And upgrading blindly without
reading the documentation of what that upgrade might do does not earn you
much sympathy on this list.
The longer you go without upgrading, the more likely you are to find all
sorts of similar surprises waiting to bite you. I find it best to either
adopt a policy of no upgrades if the behavior is not broken, or frequent
upgrades and give feedback when changes affect you but while they are
still fresh on developer's minds to be fixed. And as always, with open
source you can demand a full refund for the price you paid (after all,
bash is licensed under the GPL, which states there is no warranty).
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGmZg084KuGfSFAYARAszjAJ9qhMEop4PmAh3iDSpgzcvsYbLrtgCgnJiD
4BkdxPnDYXOCXY0FrsDzBaM=
=Mfut
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -