From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Failure building standalone
Date: Fri, 21 Jun 2013 13:11:33 +0200 [thread overview]
Message-ID: <B1549BCB-A50F-4CF4-B0CD-7193E05129C4@web.de> (raw)
In-Reply-To: <CALBOmsYVCL9TodufQSMaHkvf1HQ0PN2OcCD25q44bd1=MQshkQ@mail.gmail.com>
Hi Mojca,
I agree with you fully. It was just a thought.
The problem is most likely a bug in the port.
I had figured that first-setup.sh should be run anyway
using chmod should do the trick. In other words for cygwin
first-setup.sh cleans up what has gone wrong during transfer.
regards
Keith.
Am 21.06.2013 um 11:16 schrieb Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
> On Fri, Jun 21, 2013 at 9:54 AM, Keith J. Schultz wrote:
>> Hi All, Mojca,
>>
>> please excuse my ignorance of the inner workings of windows, but
>> would it not be possible to have the permissions corrected by the first-setup.sh
>> script after the rsync?
>
> (I'm not sure to which part you were replying.)
>
> Sure it could, but it's way better if the original file on the server
> already has the right permissions, else rsync will keep reverting the
> change, over and over again. (We are talking about using cygwin
> directly now.)
>
>
> The problems that we had on native windows (using cygwin's rsync only)
> was that even with proper permissions on the server, cygwin did
> something very bad/weird with permissions on the client's side, so the
> resulting binaries were completely useless. Of course, running chmod
> helped, but that's a weird cure because it has to be repeated after
> each sync. Each sync "fixes" (= destroys) permissions again. Using the
> weird nontsec setting solved the problem, even though I still believe
> that that could be considered a bug in rsync or its port to Windows.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-06-21 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 13:18 hwitloc
2013-06-20 13:34 ` Mojca Miklavec
2013-06-20 16:39 ` hwitloc
2013-06-21 5:56 ` Mojca Miklavec
2013-06-21 7:54 ` Keith J. Schultz
2013-06-21 9:16 ` Mojca Miklavec
2013-06-21 11:11 ` Keith J. Schultz [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=B1549BCB-A50F-4CF4-B0CD-7193E05129C4@web.de \
--to=keithjschultz@web.de \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).