X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=mZHwGaDckXuUIDTG
	/RR7sxoN7W+ubWWc1cZ80j6/O86zG8h1yBIMsOUQwDcnVZYsZMo3tfPQfz9T3DaY
	vHsj5eLv9COICDakMhn6GTL1HOlsGaF3X7PXJNDg0yTLadHA4pIFA0A7OgWUOn9O
	Vu+6KGg6goOgdHrOXfgC8lYf7N8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=HGE9DgVi8KjRhi/nvlgzcE
	ZQECY=; b=UEPH6vrxd+mYEJQTOr7DwfdVheq7+kLmpbNhREPdIhnpP+7CgM4B2c
	MbZmJGliZ7U9cxD2bwRisO8dBevfRbsRvH5pFd3SYyYeUpR+VsXVUAGOBm20/mY9
	ZQPaGt4N+BwVm/yVTpSugMRsI3kkzueC+CZBH6aRYxxZhTvCj6zvI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: vms173017pub.verizon.net
Message-id: <534350BD.9040806@cygwin.com>
Date: Mon, 07 Apr 2014 21:28:29 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
References: <loom DOT 20140403T003453-906 AT post DOT gmane DOT org> <20140404083359 DOT GD2508 AT calimero DOT vinschen DOT de> <loom DOT 20140404T113717-470 AT post DOT gmane DOT org> <20140404113738 DOT GF2508 AT calimero DOT vinschen DOT de> <loom DOT 20140407T124141-753 AT post DOT gmane DOT org> <20140407112313 DOT GA17922 AT calimero DOT vinschen DOT de> <5342D299 DOT 1040101 AT cygwin DOT com> <loom DOT 20140407T225832-327 AT post DOT gmane DOT org> <534322E8 DOT 8070701 AT cygwin DOT com> <alpine DOT LNX DOT 2 DOT 00 DOT 1404071509070 DOT 9344 AT ming DOT fruitbat DOT org>
In-reply-to: <alpine.LNX.2.00.1404071509070.9344@ming.fruitbat.org>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 4/7/2014 6:41 PM, Peter A. Castro wrote:
<snip>

> Geetings, Larry,
>
> Some comments about this (sorry if this is off-tipic):

Since you're providing this Cygwin service, I don't consider information
about this service to be off-topic.  And, of course, if *I* don't consider
it off-topic, it certainly can't be. ;-)

> 1) There used to be a directory to pull the snapshots, but that's been
>     removed or otherwise made inaccessable a while ago, so archving the
>     snapshots has been impossible for me.

Understood.  Yeah, access to "snapshots", among others, is turned off to
robots.  I'd say check with Chris on this one to see if there could be
some accommodation here.

> 2) Packaging changes of setup.exe have made extracting the version string
>     impossible, save for actually running setup, which isn't something I'm
>     going to do on a daily basis.  If there is a method of extracting this
>     info from it, please do tell me how.

I'm assuming it used to just be in the RC file in the past.  Didn't look
in the history to trace it back.  But now it is generated and put in
setup_version.c as a global constant setup_version.

> 3) The format of setup.ini hasn't changed in any significant way that
>     prevents newer versions of setup from working with older versions of
>     the achive, and vise-versa, so it hasn't been worth doing regular
>     achives of setup.  Mostly I tell people to grab the lastest setup and
>     try it first.

Yes, generally, this should work and I agree that this is the first,
easiest answer if there is no corresponding setup for a particular date.  I
was under the impression that you were also pulling setups with each
release.  That, of course, is no guarantee of direct correspondence
either but it's close.  No matter.

>     The exceptions are for the Legacy release (hard coded for -legacy)
>     as well as the preview (-2) release, but that, again, was most about
>     the name of the setup file and the initial release path names.
>     So, there really hasn't been much incentive to archive setup.
>
>     That being said, I do have a Legacy and a -2 setup versions available
>     for those that need them, as well as some other older releases of
>     setup, just in case.

Yes, I noticed.  That's a "Good Thing"(tm).  :-)

Thanks,


-- 
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