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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=dUIDE1Vg5Jwwzbm4 s7KIcVqXQUIN6I7+fte14x8DBVVxBWd6LjwxhTVC1G8TNEisnBNuTZ7DQIkLE3In SGCSprbqigbobYLgMWwPNL2ok58WUL7Z/dvRwtCO4ob2nbpfzkWVuFHtOqdJ0S1D wTvLTAGMyjK6vjY3M5COsbaRUtY= 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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=EZCNgpD3lT4GuMzVs5QUgM L1rRw=; b=OLlA7w3VbLfI0mnfzKLr/7RuE5dp3mAliwx5uh3YbmGlE5XRU8CZWB Sb+NZihZmq+W2BIB5Dp0QxOnejycd694FSN/o4wWsemQ22rbIcRjyvoT1Li3HwM7 n1xCUgrdXi5pNAHJKeP5flVOG0Phdd6BG3duIxoa/doY3FvoCt7Ds= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.0 required=5.0 tests=AWL,BAYES_40,RDNS_DYNAMIC,SPF_HELO_PASS,SPF_PASS,TVD_RCVD_IP autolearn=no version=3.3.2 X-HELO: mail.acarver.net Subject: Re: Re: [ANNOUNCEMENT] Early Deprecation Notice: Windows XP and Server 2003 support To: cygwin AT cygwin DOT com References: From: AC Message-ID: <55DE5A23.9080406@acarver.net> Date: Wed, 26 Aug 2015 17:30:27 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 2015-08-26 06:56, Stephen John Smoogen wrote: > On 26 August 2015 at 07:42, Andrey Repin wrote: >> Greetings, Stephen John Smoogen! >> >>>> Anyway, on the topic: All I could ask is to give us a notice when the final >>>> build for XP is available, so that we could prepare own mirrors. >> >>> You will need more than mirrors. You will need to set up a parallel >>> stack of builders and other tools because this will be a fork of >>> anything compiled against Cygwin from then on. You will also need to >>> look at how you are handling any bugs or problems utilities have in >>> rebuilding (but that is a longer term issue). Having had to do this in >>> the past, it will be better if you try to call this something >>> different. The reason being is that if you keep the name then when a >>> support ticket comes in from a user with Cygwin is it yours.. is it >>> the one they downloaded from the main site.. is it a version in >>> between? >> >> You're misunderstanding my daily use of Cygwin. I'm not compiling anything, >> not cygwin-related anyway. >> I'm using it as a bridging gap between sane scripting abilities of dash/make >> and insane requirements of compiling tools such as BRCC. >> And since Vista+ doesn't have support for 16-bit subsystem, I need XP VM to >> compile my projects. >> > > Ah ok. If it is just a one man operation then an archive of the trees > at a certain time are all that is needed. If you have a large Windows > XP environment you are rolling out something to then you need to make > sure you can compile and deal with the 'forked' version... which I am > guessing that some segment of XP admins have to do. > Is there a document somewhere that can describe this process of making a mirror? I have two XP machines that I won't be able to upgrade and I just want to make sure I can reinstall Cygwin packages if needed. -- 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