Mail Archives: cygwin/2002/10/21/11:44:00
> -----Original Message-----
> From: William A. Hoffman [mailto:billlist AT nycap DOT rr DOT com]
> Sent: Monday, October 21, 2002 10:12 AM
> To: cygwin AT cygwin DOT com
> Subject: Latest update problems (ntsec and file permissions, I think)
>
> Once I did that, things were better. Is this a problem that is going
> to be fixes, or are people supposed to know that they have to run
> mkpasswd -du after running setup? BTW, I also tried setting CYGWIN to
> nontsec, but this had no effect on the problem.
>
> If a new user were to try cygwin right now, I think they
> would be a bit
> confused.
>
> -Bill
Personally, I watch the list and am more careful now about upgrading a box I use in production. This can be intimidating to new users, especially when the "norm" is to expect a Setup program to present you with Release Notes.
Cygwin reminds me of running the "testing" tree of Debian: something is updated every day, and by participating in this tree you assume a higher level of risk than "usual" Windows software.
I think what is sorely needed is a "tagged release", or bundled packages. The way this could work is you are locked into a version set, and can add and remove packages without always getting the "latest" code. The benefit here would be a set of "known issues" for the release, and a proper set of Release Notes could be made for each release.
I get the impression patches for "releases" and "show release notes" would be accepted (things I couldn't offer).
-Scott
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -