From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 501 invoked by alias); 30 Apr 2013 00:25:52 -0000 Mailing-List: contact cygwin-developers-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner@cygwin.com Mail-Followup-To: cygwin-developers@cygwin.com Received: (qmail 488 invoked by uid 89); 30 Apr 2013 00:25:52 -0000 X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1 Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 30 Apr 2013 00:25:51 +0000 Received: from pool-173-76-41-247.bstnma.fios.verizon.net ([173.76.41.247] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1UWyOD-0004Kv-F8 for cygwin-developers@cygwin.com; Tue, 30 Apr 2013 00:25:49 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 5F9D760051 for ; Mon, 29 Apr 2013 20:25:48 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+zZCCqXF3roehhDjazP2+F Date: Tue, 30 Apr 2013 00:25:00 -0000 From: Christopher Faylor To: cygwin-developers@cygwin.com Subject: Re: utility to update existing cygwin symlinks to native format? (was Re: native symlink) Message-ID: <20130430002548.GA7635@ednor.casa.cgf.cx> Reply-To: cygwin-developers@cygwin.com Mail-Followup-To: cygwin-developers@cygwin.com References: <20130403152907.GD2468@calimero.vinschen.de> <20130424103450.GM26397@calimero.vinschen.de> <5177CABF.8040406@openafs.org> <20130424125043.GA18673@calimero.vinschen.de> <51781CA4.3040103@openafs.org> <20130424181412.GB26397@calimero.vinschen.de> <3B3671F5-EBFE-480B-B592-90BA2270BDA6@mac.com> <42E7B9C6-1A6A-43D7-84B3-AEDD25EF4507@mac.com> <517F061D.5080201@cygwin.com> <671E245A-BDCD-4F46-90B7-9E73301126C1@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <671E245A-BDCD-4F46-90B7-9E73301126C1@mac.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2013-04/txt/msg00077.txt.bz2 On Mon, Apr 29, 2013 at 04:49:33PM -0700, James Gregurich wrote: > > >On Apr 29, 2013, at 4:45 PM, "Larry Hall (Cygwin Developers)" wrote: > >> On 4/29/2013 6:04 PM, James Gregurich wrote: >>> I have not gotten a response to this question yet. I'd like to get into >>> a position to roll this version of cygwin out so that we can use it daily and >>> look for glitches, but I do need the ability to upgrade existing symlinks >>> before that is feasible. Is there an answer to my question? >> >> You'll have to wait until Corinna returns from vacation at least for the >> answer to whether or not this has been done already. I can't say if >> you've inspired Corinna (or someone else) to implement this for you. >> If not, you may have to create your own utility for this part. > >ok. thanks for the info > >The utility that I wrote for myself depends upon an exposed API >function in path.cc since all the logic to handle the internal format >of the cygwin symlink file is contained in path.cc. I could easily >write one for myself if such a function were exposed as a public API. >I'd just need the specs to use the call. If you're asking "Did Corinna write a utility to do this?" the answer is extremely likely to be "No" since she would have mentioned it if she had. If you're asking "Will Corinna write a utility to do this?" I suspect that the answer is likely also "No". cgf