From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: attention alternatives maintainer
Date: Fri, 16 Jul 2021 07:18:34 +0200 [thread overview]
Message-ID: <87k0lq96qd.fsf@Otto.invalid> (raw)
In-Reply-To: <CAJ1FpuMzcZU_2Lrp_SciRy10OzCaL_ji90OukPWEa-LtRCJzUA@mail.gmail.com> (Doug Henderson via Cygwin-apps's message of "Thu, 15 Jul 2021 17:07:34 -0600")
Doug Henderson via Cygwin-apps writes:
> Please update alternatives to work properly for a first time install
> of an alternative when CYGWIN=winsymlinks:nativestrict.
I do not think of this as a bug in alternatives. POSIX programs that
create symlinks to non-existing files are perfectly valid and they don't
need to care whether they are pointing to files or directories either.
A dangling POSIX symlink resolves once its target comes into existence.
> In order to make it run I must set CYGWIN=winsymlinks:native, run the
> postinstall script in an elevated shell (or from setup). Then I can
> restore CYGWIN=winsymlinks:nativestrict. I think the link target must
> be created before the symlink is created. Without looking at the code,
> I suspect the order of two symlink needs to be reversed.
No, setup should ignore the CYGWIN settings. These are for the user,
not the installation. I wouldn't mind if there was an option to force
this behaviour so people wanting to experiment with it can do it, but
then they have to deal with the inevitable fallout themselves.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2021-07-16 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 23:07 Doug Henderson
2021-07-16 1:56 ` Ken Brown
2021-07-16 1:58 ` Ken Brown
2021-07-16 19:19 ` Doug Henderson
2021-07-17 5:20 ` ASSI
2021-07-16 5:18 ` ASSI [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=87k0lq96qd.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).