From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) by sourceware.org (Postfix) with ESMTPS id 3C409384607A for ; Thu, 27 Aug 2020 09:45:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C409384607A Received: by mail-vk1-xa2a.google.com with SMTP id x187so1105568vkc.1 for ; Thu, 27 Aug 2020 02:45:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=PjWwW6rZTIt6OxPRqRpyLLB3h4Ih+2pCIl8egcqxeFw=; b=uZ2hp2HYJL+B/o+WFVwZbFWN/K0T0bGE+eaD7J+Dph72h41f55BSlnY2BPMWhUAY8d 06J3Wm6v+rDSQmSx8CFZbrarEmLVnQS6zl8MbBY68WyMgRuesE1+cbOpx8z/+W2cuoa/ dO81KETSWfZvvn6dFOCMoBlB24MoY3cL5Ad1tGzc1F9q8JS+anN+ovi7DIP+2kySXvIE l+o4VRMQdtY576v9p3Qyk/w/oFtG3+WA90zcrihm9T6PYIx5zVnpSIIrLre+3Krcygp+ eHg8qW6hKtG+dMeeRZG8WYCFFtxA1fJFTA5IgOVXMKnbduCO68+yAn8k/fK4vSL8HwlF Tzrw== X-Gm-Message-State: AOAM531rmQZzq24SQIqwTWa+su57qJ3xhUS8G/VBkMaVK6ze9CJNUboV CRAw8oR1sxYlLjSYGDx6nyDCLK7JE0E+e7qKkomldY2O0wjA+Q== X-Google-Smtp-Source: ABdhPJxJgfOGaFMXFPNUAfCOkvhmBnGF0BgFnfqoLubdmvLT9QJ+3nMAwLy8A7JMi6LVCWhWOiH63ZJ22oKbjlyxt28= X-Received: by 2002:a05:6122:2d1:: with SMTP id k17mr11656516vki.20.1598521499462; Thu, 27 Aug 2020 02:44:59 -0700 (PDT) MIME-Version: 1.0 References: <875z95tg5c.fsf@Rainer.invalid> <1f4a80f7-0e14-1641-3fce-317ac2a6dd00@dronecode.org.uk> <20200827090010.GZ3272@calimero.vinschen.de> In-Reply-To: <20200827090010.GZ3272@calimero.vinschen.de> From: Michael Wild Date: Thu, 27 Aug 2020 11:44:41 +0200 Message-ID: Subject: Re: Forcing setup.exe not to create WSL symlinks To: The Cygwin Mailing List X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2020 09:45:02 -0000 On Thu, Aug 27, 2020 at 11:02 AM Corinna Vinschen wrote: > On Aug 27 07:48, Michael Wild via Cygwin wrote: > > On Wed, Aug 26, 2020 at 10:57 PM Jon Turney wrote: > > > > > > > > It turns out to be the case that setup doesn't propagate the CYGWIN > > > environment variable into the environment for scripts it runs, so > > > setting that isn't going to make any difference. That should probably > > > be considered a bug. > > > > > > However, even if that's fixed, there's no value for winsymlinks in > > > CYGWIN env var to specify the behaviour of Cygwin 3.1.4 and previous > > > (i.e. always create traditional symlinks, don't use WSL symlink reparse > > > points) > > > > > > > Thanks Jon for the elaboration. Isn't winsymlinks=lnk supposed to do this > > per the documentation? Could Corinna be convinced to include an option > > where this can be done? To be honest, my hopes are greater to get this > > worked-around in a useful timeframe from the Cygwin side than getting the > > proper fix into Docker. > > Isn't it sufficient to fix setup so you can create lnk-style symlinks in > your scenario? The CYGWIN env variable and the number of options is > such a mess. > > > Corinna > I am right now modifying setup to not sanitize CYGWIN away when invoking the post-install scripts and then will report back. Michael