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:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=Y+do6+lFYf5R6rREbk5/Pb7LeOfwdVOsK7V1OPhc+Ma gPsqH3LIhhRSAcI6Y4Yj2i9vbRRwK7Ss3r+TKoBPUjGFEoLNFEUIhIg/Dw6q9gn5 eUWZzHwQ0XsybO1+8edw2764ClCJaWM/JSqXodaa5i/kfV/fmqz3xw7HPeNM5SUI = 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:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=2shmPQ/iXvqh/3cMnmzR3Q0CEe4=; b=xJ2VrKGC0TKq9iwTD oXGduX25cC3ZCrKAaQ3Rw00GXzGcXXrfKPG/bvWW8WuBF92V07n5cUff4uo4VrAY xpY54KZA6tJAxLK+zl++xnkn7SY04f+5RNLWAnk0AYVtoOzyvqrMj9aOtRYHmQG/ Rkm9wKLn5pKLzKrajeQEVvBdLc= 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=-4.5 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Hx-languages-length:1466, H*MI:sk:nsthp6$, mounted X-HELO: Ishtar.sc.tlinx.org Message-ID: <57F40138.2030409@tlinx.org> Date: Tue, 04 Oct 2016 12:21:28 -0700 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Native symlinks and setup.exe References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Thorsten Kampe wrote: > Tar's task is to unpack what's in the archive. So converting is out > of question. You can ask the maintainer of the affected packages to > create the symlinks in the postinstall script. --- Is it a "special" tar, or is it the normal version of tar that runs under Cygwin? I would assume that the install scripts run under the cygwin-environment. That includes paying attention to the global value of CYGWIN. If you set CYGWIN in your windows environment variables (recommended), then it will always be set before any cygwin or setup program runs. Setup isn't going to explicitly clear CYGWIN of its values, unless they *happen* to be "invalid" -- and even then, I doubt it would modify the user-set value of CYGWIN. When I install programs, tar has always honored the global value of CYGWIN I set in the system env vars. (System is recommended over User Env, since cygwin can run as multiple users, and if you want consistent cygwin operation, you should set it before any cygwin processes have started. Is someone claiming that values in the System-Env var CYGWIN are ignored by programs being installed? NOTE: it is known and considered a "feature", that Cygwin ignores MS-mountpoints mounted with mountd or linkd (link directory) and treats them as symlinks. This prohibits user control and redirection of installed programs and disables the linux equivalent of mount --bind "thisdir" "onthisdir". -- 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