Re: crazy default permissions

On 10/5/2016 12:40 AM, Marco Atzeri wrote: On 05/10/2016 06:31, Mitch Deoudes wrote: mkdir has suddenly started creating directories with strange permissions. As far as I can tell, it's related to making directories nested inside other directories that were also created within cygwin. As you

Re: crazy default permissions

On 05/10/2016 06:31, Mitch Deoudes wrote: mkdir has suddenly started creating directories with strange permissions. As far as I can tell, it's related to making directories nested inside other directories that were also created within cygwin. As you create deeper and deeper nestings, the perms

crazy default permissions

mkdir has suddenly started creating directories with strange permissions. As far as I can tell, it's related to making directories nested inside other directories that were also created within cygwin. As you create deeper and deeper nestings, the perms get more and more screwed up. It

Re: [ITP] Perl distributions

On 03/10/2016 11:45, Achim Gratz wrote: perl-Archive-Extract (as requested by D. Stacey) perl-ExtUtilsHelpers (an indirect build dependency of perl-Readonly) added. I also would like to get co-maintainership for perl-MIME-tools perl-MailTools which are behind their latest releases and

Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist

On 05/10/2016 05:00, Rinrin wrote: Hi Gene: I made a patch for my private use. First of all, you should setup `nativenocheck` in CYGWIN environment variable to enable this feature. If the target does not exist, it will check the last digit of target path, for '/' it will create a instead

Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist

Hi Gene: I made a patch for my private use. First of all, you should setup `nativenocheck` in CYGWIN environment variable to enable this feature. If the target does not exist, it will check the last digit of target path, for '/' it will create a instead of 在 2016/4/30 8:14, Gene

Re: Native symlinks and setup.exe

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

Re: Native symlinks and setup.exe

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

Re: Latest "setup-x86(_64)?\.exe" version supporting WinXP

On 04/10/16 20:38, Peter A. Castro wrote: The latest version of Setup is 2.876 (as of this writing). I have no idea if it can be run on XP or not though I suspect it can. The latest version of Setup does not run on XP. Details in the announcement:

[ANNOUNCEMENT] Updated: weechat-1.6-1

Version 1.6-1 of "weechat" has been uploaded. ChangeLog and release notes: https://weechat.org/files/changelog/ChangeLog-1.6.html https://weechat.org/files/releasenotes/ReleaseNotes-1.6.html DESCRIPTION WeeChat is a fast, light and extensible chat client. It runs on many platforms like Linux,

Updated: weechat-1.6-1

Version 1.6-1 of "weechat" has been uploaded. ChangeLog and release notes: https://weechat.org/files/changelog/ChangeLog-1.6.html https://weechat.org/files/releasenotes/ReleaseNotes-1.6.html DESCRIPTION WeeChat is a fast, light and extensible chat client. It runs on many platforms like Linux,

Re: Native symlinks and setup.exe

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

Re: Native symlinks and setup.exe

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

Re: Native symlinks and setup.exe

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

Re: Native symlinks and setup.exe

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

Re: Latest "setup-x86(_64)?\.exe" version supporting WinXP

On Tue, 4 Oct 2016, Sophoklis Goumas wrote: Date: Tue, 4 Oct 2016 14:02:44 +0300 From: Sophoklis Goumas To: cygwin@cygwin.com Subject: Latest "setup-x86(_64)?\.exe" version supporting WinXP Hello. Greetings, Sophoklis, I'm seeing some contradicting clues from

Re: Native symlinks and setup.exe

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?

[ITP] gambas3

Hi, I have packaged gambas3, a development environment similar to Visual Basic, and would like to become a maintainer for it. Gambas is available at http://gambas.sf.net and is licensed under GPLv2 or later. The major GNU/Linux distributions include it in their repositories, e.g. Debian:

Re: Native symlinks and setup.exe

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

Re: Latest "setup-x86(_64)?\.exe" version supporting WinXP

On 4.10.2016 13:02, Sophoklis Goumas wrote: Would you also, please, confirm the validity of those files? Hello Sophoklis, I can confirm, that sha1sum of setup-x86_64-2.874.exe is valid. Unfortunately, I don't have setup-x86-2.874.exe archived. Vlado -- Problem reports:

Latest "setup-x86(_64)?\.exe" version supporting WinXP

Hello. I'm seeing some contradicting clues from cygwin.com and fruitbat.org's Cygwin Time Machine [1] as to which is the latest version of "setup-x86(_64)?\.exe" with WinXP "support". Something like: > The previous Cygwin version 2.5.2 was the last version supporting Windows XP > and Server

Automated Cygwin installation on a Google VM

Hey everyone! We are trying to set up an automated Cygwin install on a Windows Server 2012 R2 VM in the Google cloud. The idea is to build a script that makes sure Icinga is able to connect to the server via SSH, for monitoring reasons. Here is what we came up with: --- # Cygwin installation +

Re: Native symlinks and setup.exe

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