Mail Archives: cygwin/2011/01/07/15:32:40
On 1/7/2011 3:12 PM, Larry W. Virden wrote:
> When considering building a basically "frozen" version of cygwin - that is
> to say, downloading, configuring, and building a disk image, then turning
> that disk image into a MSI for installation purposes (in an environment where
> this is being done because users will not have Windows 7 permissions to
> perform additional setup or package manipulations), what version of cygwin
> should be considered stable for developer use? The environment expects to
> use cygwin/x , bash, and a variety of commonly used "unix-like" applications
> (awk, perl, wc, cat, make, java, ...).
>
> Certainly each alpha and beta release contains bug fixes and enhancements
> that might be useful for the developer to have. However, in at least this
> shop, there isn't enough time available for software integrators to update
> the installation image daily and push it out. Instead, there is typically a
> point in time in which a project is created which draws a line, picks the
> recommended release at that point, bundles things up, and then, in the future
> as problems or features demand, a new project is proposed, scheduled,
> staffed, and executed for creating a new release.
>
> Is cygwin 1.7.6 considered stable for use on 32 bit Windows 7? Or do we need
> to drop back farther?
The current release is 1.7.7. I use this on Windows 7 32 and 64 bits.
Whether you feel it meets your needs is, of course, your decision.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -