Re: attention alternatives maintainer
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
Re: attention alternatives maintainer
On 7/15/2021 9:56 PM, Ken Brown via Cygwin-apps wrote: On 7/15/2021 7:07 PM, Doug Henderson via Cygwin-apps wrote: Please update alternatives to work properly for a first time install of an alternative when CYGWIN=winsymlinks:nativestrict. Cygwin doesn't have an alternatives maintainer. Would you like to volunteer? If so, start at https://cygwin.com/packages.html and follow up on the cygwin-apps mailing list if you need help. Sorry, I see you're already a package maintainer, so you know how to do it. Ken
Re: attention alternatives maintainer
On 7/15/2021 7:07 PM, Doug Henderson via Cygwin-apps wrote: Please update alternatives to work properly for a first time install of an alternative when CYGWIN=winsymlinks:nativestrict. Cygwin doesn't have an alternatives maintainer. Would you like to volunteer? If so, start at https://cygwin.com/packages.html and follow up on the cygwin-apps mailing list if you need help. Ken
attention alternatives maintainer
Please update alternatives to work properly for a first time install of an alternative when CYGWIN=winsymlinks:nativestrict. See the recent thread on the cygwin mailing list with subject Setup shows errors from gnuplot-base.dash and python38-devel.sh In essence, when CYGWIN=winsymlinks:nativestrict., the first time it runs, a postinstall script for a package that uses alternatives will fail. Once it has succeeded once, it will subsequently run without error. 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. The basis for the problem is the difference between POSIX and Windows symlinks.As I understand it, Windows symlinks need to :"know" if the target is a file or directory, while the POSIX symlink does not require the target to exist. Thanks, Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com
