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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=GLWemkiEcVKYhx1I
	sXiC27aaxoKvbqc8C/MNGsF0BfV63eaiLMqEI4g3K0+C7v0gzYeWa7KdoqLFJ5P/
	HO7gVcjLoq2YYcJjA1grleSFm5DXrT2A2QMz7RBZBe3afP+mMfZFOQTT9Km313wd
	uYmuYc1cSRW+HevMIQjoz4I1JEg=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=f3N59ltIkAkyEx6lgNdcE/
	F77lY=; b=aPMu3vgKULEZmt7iN48bpHX7Qi8IUc5YKM3AAIcZ2Ka0OeEaGYQR+E
	zXTWeQmCc0XR/ZMFcTQ5Mm1Zg4AnnUTDrVAAWPvggYYVNbj+NgVCALw6aa4ow8So
	Gv3MKqR0lJ/I8SCfHjKOek6tvGOw7H3ZCAiEwg04XFIGw+zyVn2RY=
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=1.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Sat, 6 Dec 2014 00:05:57 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <12010306738.20141206000557@yandex.ru>
To: Corinna Vinschen <cygwin AT cygwin DOT com>, cygwin AT cygwin DOT com
Subject: Re: RFC: 1.7.33 problem with user's home directory
In-Reply-To: <20141205101505.GJ3810@calimero.vinschen.de>
References: <20141110205216 DOT GJ2782 AT calimero DOT vinschen DOT de>   <0B8D23F7-0258-472D-BF38-860402FD3CDC AT etr-usa DOT com>  <20141111101821 DOT GO2782 AT calimero DOT vinschen DOT de>  <loom DOT 20141111T112847-576 AT post DOT gmane DOT org>  <20141111111437 DOT GB28012 AT calimero DOT vinschen DOT de>  <20141126205658 DOT GA9157 AT calimero DOT vinschen DOT de>  <20141204154911 DOT GH3810 AT calimero DOT vinschen DOT de>  <199481337 DOT 20141205082850 AT yandex DOT ru>  <20141205101505 DOT GJ3810 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Corinna Vinschen!

>> > I'd appreciate if those not shy to install developer snapshots would
>> > give this stuff a try in the meantime.
>> 
>> I think I'm about to make a script to install snapshots, at this rate it seems
>> the right thing to do.
>> Is there a direct way to query for the latest snapshot?

> The snapshots always have a date attached to the filename.

I mean, if there's a way to know, what is the latest available snapshot?
If I want to write a script, that fetch [and install] one.
I can parse the /snapshots/ page, of course, but this is the least desirable
choice. For multiple reasons. I would like to have a single point, that could
refer to the very latest snapshot. Even if it is something like
/snapshots/x86/cygwin-inst-latest.tar.xz redirecting to
actual latest snapshot, that'd be quite enough.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 05.12.2014, <23:12>

Sorry for my terrible english...


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