Never mind, I found it's in another repository.
The code looks quite different, adapting the symlink code from newlib
to setup doesn't look straightforward, at least to my limited C
skills.
By the way, if I have an already created symlink, how do I check (e.g.
in a bash script) whether it's native
Eric,
Before writing a patch it's wise to check if it would be accepted, now
that your position is clear, somebody might do it.
I don't think I'm up for the task, but I'd like to at least take a
look at the sources.
I've downloaded the git sources and found the link creation function
is in winsup/
On 10/04/2016 03:53 PM, Vince Rice wrote:
>>> Obviously, a political discussion is required, to decide whether it is
>>> ok, as is, or if a change in package logic would have benefits.
The easiest way to have the discussion would be to write a patch,
instead of debating about different behaviors b
Please don’t https://cygwin.com/acronyms/#TOFU.
> On 4 October 2016 at 17:56, Gerrit Haase wrote:
>> Hello Gene,
>>
>> in my opinion, it is not a setup.exe or tar problem, but I think
>> packages should not include symlinks at all. All can be created
>> postinstallation by the postinstall script
That is a good point as well, however I'm not sure what are the
opinions of Cygwin's "elders".
Would everyone vote for creating a policy like that and pushing it to
the package maintainers?
A political discussion is what I'm trying to start here :)
On 4 October 2016 at 17:56, Gerrit Haase wrote:
That is a good solution indeed, if I just want to get the result I
want, for myself.
But it's just local solution.
On 4 October 2016 at 09:57, Vlado wrote:
> On 3.10.2016 23:15, Gene Pavlovsky wrote:
>>
>> How about this kind of modification for the setup program: extract tar
>> archives into tem
Thorsten Kampe wrote:
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.
---
Is it a "special" tar, or is it the normal version of tar that
runs under Cygwin?
I
Hello Gene,
in my opinion, it is not a setup.exe or tar problem, but I think
packages should not include symlinks at all. All can be created
postinstallation by the postinstall script, inside Cygwin and the
users environment it is running on.
Obviously, a political discussion is required, to deci
On 3.10.2016 23:15, Gene Pavlovsky wrote:
How about this kind of modification for the setup program: extract tar
archives into temp dir, after that search that temp dir for symlinks,
Hi, Gene.
Maybe You can consider to write and run simple script:
- find all links (find -type l)
- read target
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 optio
* 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 symlink
Thorsten,
That's a great pointer. I've just investigated using the `flex`
package as an example.
Untarring flex-2.6.1-1.tar.xz, usr/bin/flex++ is extracted as a Cygwin
symlink to usr/bin/flex.exe.
If I create a native symlink to flex.exe, tar it all up to a new tar
archive, then extract it somewhe
Greetings, Gene Pavlovsky!
> I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
> Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
> After that I ran setup-x86_64.exe and installed cygwin64.
> The symlinks to .exe files in bin, created by setup, are not n
* Gene Pavlovsky (Sat, 1 Oct 2016 18:52:47 +0300)
>
> I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
> Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
> After that I ran setup-x86_64.exe and installed cygwin64.
> The symlinks to .exe files in bin, cr
On 01.10.2016 23:32, Vlado wrote:
> On 1.10.2016 17:52, Gene Pavlovsky wrote:
>> Before running setup.exe I've set the system env var
>> CYGWIN=winsymlinks:native
>> After that I ran setup-x86_64.exe and installed cygwin64.
>> The symlinks to .exe files in bin, created by setup, are not native
>>
On 1.10.2016 17:52, Gene Pavlovsky wrote:
Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
After that I ran setup-x86_64.exe and installed cygwin64.
The symlinks to .exe files in bin, created by setup, are not native
symlinks, they are cygwin symlinks. Apparently, se
I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
After that I ran setup-x86_64.exe and installed cygwin64.
The symlinks to .exe files in bin, created by setup, are not native
symlinks, they are cygwin syml
17 matches
Mail list logo
