public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Rainer Emrich <rainer@emrich-ebersheim.de>, cygwin@cygwin.com
Subject: Re: Change in logical link behaviour
Date: Wed, 04 Mar 2020 19:45:00 -0000	[thread overview]
Message-ID: <827792296.20200304215647@yandex.ru> (raw)
In-Reply-To: <99c7b27b-9ea8-cf1e-d5ce-afc685246f97@emrich-ebersheim.de>

Greetings, Rainer Emrich!

> Ok, so I can't rely on powershell here. Is there a recommended procedure
> for what I try in a script?

> Check if the current cygwin environment is able to create native symlinks.

There's more than just Cygwin involved.

1. Target FS may not support symlinks.
2. User may not have necessary permission.

If, for some reason, you DO actually required to create symlinks, go with
winsymlinks:native, they are safer for use and relatively well supported in
other tools.


-- 
With best regards,
Andrey Repin
Wednesday, March 4, 2020 21:50:02

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

      parent reply	other threads:[~2020-03-04 19:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 13:11 Rainer Emrich
2020-03-01  2:05 ` Andrey Repin
2020-03-01 17:01   ` Rainer Emrich
2020-03-02 16:49 ` Corinna Vinschen
2020-03-03 13:17   ` Rainer Emrich
2020-03-03 13:39     ` Rainer Emrich
2020-03-03 14:19     ` Corinna Vinschen
2020-03-03 14:27       ` Rainer Emrich
2020-03-03 14:31         ` Rainer Emrich
2020-03-03 16:05         ` Corinna Vinschen
2020-03-03 16:32           ` Corinna Vinschen
2020-03-03 16:41             ` Rainer Emrich
2020-03-03 16:46               ` Rainer Emrich
2020-03-03 17:34               ` Corinna Vinschen
2020-03-03 21:43                 ` Rainer Emrich
2020-03-04 19:45               ` Andrey Repin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=827792296.20200304215647@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=rainer@emrich-ebersheim.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).