This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Downloading previous versions of Cygwin

Thank you for the details.  That answers my questions.  My process has always been, when a version is available, I use the installer to "download from internet".  At that time, I download all the binaries (and sometimes sources).  That way, a specific version of cygwin is saved (archived for my purposes).  

Unfortunately, I don't have such an archive for v1.3.17.  The nearest version I have archived is v1.3.22.

Thanks again for your support.  The sshd built into cygwin makes it easy to execute remote processes on a Win2k workstation.  There are other shareware utilities for doing this, but the other tools built into cygwin makes this a very useful choice.


Matt Berney
Polyserve, Inc.

-----Original Message-----
From: Igor Pechtchanski []
Sent: Thursday, October 09, 2003 6:35 PM
To: Matt Berney
Subject: RE: Downloading previous versions of Cygwin

On Thu, 9 Oct 2003, Matt Berney wrote:

> For testing purposes, and limiting the number of variables, it is
> essential that we use one-and-only-one version of cygwin.  The
> variations in the tools and utilities may introduce subtle and
> undesirable side-effects.  Once a major release cycle is achieved, then
> the decision to upgrade the cygwin version is made.  However, changing
> the tools "mid-flight" is a dangerous precedent to set in a QA
> department.

I understand the sentiment completely.  As I mentioned, your best bet is
to distribute the versions of the Cygwin packages needed for your tools
along with the tools themselves (don't forget to distribute the sources,
as required by the GPL).

> With that said, we did try to move to v1.5.X, but ran into numerous
> problems surrounding ssh and other process handling problems.

It would be a great help if you could outline the exact problems that
you've had (as these would be regressions from 1.3.*, FWICS), as long as
they aren't fixed in the latest DLL version (currently 1.5.5).

> I understand your point.  If one wants support from the community, then
> one must be using the latest version.  But, sometimes, that is just not
> in the cards.

I didn't mean to imply that this was your only option, just wanted to make
you aware of this angle.

> I didn't see an answer to my question, however.  Is there a way to find
> a specific version of cygwin (and all associated tools and utilities)?
> I could search through the mirror sites, but it would be nice if the
> cygwin installer allowed for "version X and associated utilities".

Cygwin is not a distribution; every package gets updated whenever the
volunteer maintainers decide to update it, so I doubt you'd find a true
snapshot of the Cygwin packages somewhere, unless some mirror is extremely
stale (1.3.17 was a while ago).  You could do one of two things: create
your own mirror with a setup.ini (see <>) and
use the packages from the cache in your local package directory to
populate it (you will have to make sure you have the appropriate sources),
or try to get a snapshot of some mirror's directory or older setup.ini on,
say, <> (if you're lucky) and search for the
specific source and binary tarballs.

Unfortunately, there isn't much else you can do, except try to get your
tools working with 1.5.5 and grab the sources and binaries for your own
mirror (this way you can make sure you have everything you need).

> Thanks for your prompt response.
> Matt Berney
> Polyserve, Inc.

You are welcome,

> -----Original Message-----
> From: Igor Pechtchanski []
> Sent: Thursday, October 09, 2003 5:39 PM
> To: Matt Berney
> Cc:
> Subject: Re: Downloading previous versions of Cygwin
> On Thu, 9 Oct 2003, Matt Berney wrote:
> > We have standardized on a previous version of cygwin (1.3.17).  It
> > appears to be quite stable for our purposes.  But, I haven't found a way
> > to download that version (and all associated tools & utilities
> > associated with it).  Does someone out there have a solution for this?
> > I searched the archives, but couldn't find anything relevant.
> >
> > Thanks in advance,
> > Matt Berney
> Your best bet is to find a (very) stale mirror, or to distribute the DLL
> (with associated sources) yourself.  However, by doing so you're
> essentially depriving your users from any support on this list, as the
> first recommendation would be to upgrade.  Is there a particular reason
> why your tools won't work with the latest version of Cygwin?  It should be
> backward-compatible.
>         Igor

      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]