From c10a2eabb480edbde03608535c4813a8ae636f1e Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Wed, 17 Aug 2016 23:50:50 +0200 Subject: README update --- .README.md | 13 ------------- .appdata/appdata.sh | 12 ++++++++++++ 2 files changed, 12 insertions(+), 13 deletions(-) diff --git a/.README.md b/.README.md index 33a792b..1e5b4c0 100644 --- a/.README.md +++ b/.README.md @@ -3,19 +3,6 @@ Cygwin configuration files My Cygwin home (`~`) configuration files. -Prerequisites -------------- - -Some of the functionality relies on the availability of native symlinks. -Those are indeed available on NTFS, but require Administrator privileges for -creation. -It likely won't bother you as long as you don't use the functions from -".bashrc" that actually create symbolic links (you will likely see `ln` -complaining about some access being denied in case you do). - -Your `CYGWIN` environment variable (on Windows) **must** include either -`winsymlinks:native` or `winsymlinks:nativestrict`! - Deployment ---------- diff --git a/.appdata/appdata.sh b/.appdata/appdata.sh index 582af9a..ab48541 100644 --- a/.appdata/appdata.sh +++ b/.appdata/appdata.sh @@ -5,6 +5,18 @@ # For details, see https://github.com/egor-tensin/cygwin-home. # Distributed under the MIT License. +# This relies on the availability of native symlinks. +# Those are indeed available on NTFS, but require Administrator privileges for +# creation. +# It likely won't bother you as long as you don't use the functions defined in +# this file. +# In any case, you will see `ln` complaining about some access being denied in +# case something goes wrong. +# +# Remember that in order to force `ln` to use native NTFS symlinks, your +# `CYGWIN` Windows environment variable value **must** include either +# `winsymlinks:native` or `winsymlinks:nativestrict`! + ensure_symlinks_enabled() { case "${CYGWIN:-}" in *winsymlinks:native*) ;; -- cgit v1.2.3