public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup 00/11] Add options to choose symlink type (v2)
Date: Tue, 14 Sep 2021 12:53:34 +0100	[thread overview]
Message-ID: <6b011ff7-1013-7eeb-202b-635c711cc341@dronecode.org.uk> (raw)
In-Reply-To: <20210810170228.1690-1-jon.turney@dronecode.org.uk>

On 10/08/2021 18:02, Jon Turney wrote:
> Revised from [1], this adds an '--symlink-type {sys, native, wsl}' option,
> which controls the type of symlinks created by setup and the post-install
> scripts it invokes [2].

In the base install, there are 4 symlinks which can't be created using
the native method (and hence fall back to sys method):

> package          from                                     -> to                         reason
> 
> terminfo        /usr/lib/terminfo                         -> ../share/terminfo          mount table
> terminfo        /usr/share/terminfo/6a/jfbterm            -> ../6b/kon                  target is in terminfo-extra package, unpacked later as unpack order isn't dependency order (only postinstall script run order?)
> file            /usr/share/file/magic                     -> ../magic                   target is also a symlink, later in the same archive
> ca-certificates /usr/libexec/p11-kit/trust-extract-compat -> ../../bin/update-ca-trust  mount table

'mount table' means that in the current setup architecture, 'from' has 
already been translated through the mount table into a native path 
before we can try to locate 'to' relative to it, but it exists relative 
to the untranslated path.

It's probably possible to improve the handling of these cases with more 
effort.

      parent reply	other threads:[~2021-09-14 11:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 17:02 Jon Turney
2021-08-10 17:02 ` [PATCH setup 01/11] Add support for creating WSL symlinks Jon Turney
2021-08-10 17:02 ` [PATCH setup 02/11] Add support for creating native symlinks Jon Turney
2021-08-10 17:02 ` [PATCH setup 03/11] Factor out the iteration over archive files to install Jon Turney
2021-08-10 17:02 ` [PATCH setup 04/11] Add seek() method to archive and compress file classes Jon Turney
2021-08-10 17:02 ` [PATCH setup 05/11] Add separate symlink-creation phase when extracting archive Jon Turney
2021-08-10 17:02 ` [PATCH setup 06/11] Enable SeCreateSymbolicLink privilege Jon Turney
2021-08-11  8:46   ` Corinna Vinschen
2021-09-14 11:53     ` Jon Turney
2021-08-10 17:02 ` [PATCH setup 07/11] Add symlink capabilities to user-agent telemetry Jon Turney
2021-08-10 17:02 ` [PATCH setup 08/11] Factor out StringChoiceOption Jon Turney
2021-08-10 17:02 ` [PATCH setup 09/11] Add a command line option to choose symlink type used Jon Turney
2021-08-10 17:02 ` [PATCH setup 10/11] Propagate --symlink-type setting to post-install scripts Jon Turney
2021-08-10 17:02 ` [PATCH setup 11/11] Default symlink mode from CYGWIN env var Jon Turney
2021-09-14 11:53 ` Jon Turney [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=6b011ff7-1013-7eeb-202b-635c711cc341@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /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).