From: Gene Pavlovsky <gene.pavlovsky@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Native symlinks and setup.exe
Date: Tue, 04 Oct 2016 06:57:00 -0000 [thread overview]
Message-ID: <CAPTiy3NzXWSv8+kazpeXYx9EB18nQ+f+S1aSyQcAF4aMrNdqtQ@mail.gmail.com> (raw)
In-Reply-To: <nsthp6$jtq$1@blaine.gmane.org>
That makes sense but it would be a LOT of work for many people (well,
a lot of small work for many people).
How about this kind of modification for the setup program: extract tar
archives into temp dir, after that search that temp dir for symlinks,
if they don't match the current winsymlinks option, recreate them
appropriately?
I just remembered what I did when I first discovered the winsymlinks
option (already having a 32-bit Cygwin set up for a couple of years).
I tarred my entire cygwin directory, copied it over to my Linux
server, untarred it there - which created all the symlinks, including
Cygwin's symlinks, as proper symlinks, then tarred it back, copied
back to the Windows box, untarred - voila, all symlinks are created as
native. I wonder how are Cygwin vs native symlinks stored inside tar
archive - tar knows they are symlinks but also knows which ones are
native vs Cygwin's. That's a whole lot of bother, though, and now that
I know that some further package update down the line might replace
native links with Cygwin links again (didn't expect that), I wouldn't
be willing to go to that trouble.
It should work out of the box automatically, in my opinion. Cygwin
symlinks are a kluge (e.g. I can't edit them in Far manager, the way I
can adjust a native symlink), and if using Cygwin exclusively on NTFS
filesystems, supporting symlinks, I can't see any reason to have any
on my system. The proposed solution is sensible, but it spreads
responsibility among all the package maintainers, and it will take a
long time to reach.
On 3 October 2016 at 15:08, Thorsten Kampe <thorsten@thorstenkampe.de> wrote:
> * Gene Pavlovsky (Mon, 3 Oct 2016 00:46:54 +0300)
>>
>> So, when installing, the type of symlinks doesn't honor the CYGWIN
>> option since they are just unpacked by tar as is.
>>
>> The question I'm proposing now - should `tar` be modified to honor the
>> CYGWIN option and automatically convert symlinks when extracting, if
>> necessary?
>
> Tar's task is to unpack what's in the archive. So converting is out
> of question. You can ask the maintainer of the affected packages to
> create the symlinks in the postinstall script.
>
> Thorsten
>
>
> --
> 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
>
--
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
next prev parent reply other threads:[~2016-10-03 21:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 18:49 Gene Pavlovsky
2016-10-01 21:56 ` Vlado
2016-10-02 6:27 ` Herbert Stocker
2016-10-02 11:48 ` Thorsten Kampe
2016-10-02 23:35 ` Gene Pavlovsky
2016-10-03 18:26 ` Thorsten Kampe
2016-10-04 6:57 ` Gene Pavlovsky [this message]
2016-10-04 8:15 ` Vlado
2016-10-04 20:42 ` Gene Pavlovsky
2016-10-04 19:21 ` Gerrit Haase
2016-10-04 20:54 ` Gene Pavlovsky
2016-10-04 21:04 ` Vince Rice
2016-10-04 21:20 ` Eric Blake
2016-10-04 23:15 ` Gene Pavlovsky
2016-10-05 3:03 ` Gene Pavlovsky
2016-10-04 19:39 ` Linda Walsh
2016-10-02 20:08 ` Andrey Repin
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=CAPTiy3NzXWSv8+kazpeXYx9EB18nQ+f+S1aSyQcAF4aMrNdqtQ@mail.gmail.com \
--to=gene.pavlovsky@gmail.com \
--cc=cygwin@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).