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?
regards
Keith.
Am 21.06.2013 um 07:56 schrieb Mojca Miklavec mojca.miklavec.li...@gmail.com:
On Thu,
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.)
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
I tried building the standalone but ran into a snag.
Here is the error message display when I ran first-setup.sh:
sh ./first-setup.sh --modules=all --engine=luatex --context=current
receiving incremental file list
rsync: change_dir /setup/cygwin (in minimals) failed: No such
On Thu, Jun 20, 2013 at 3:18 PM, hwit...@gmail.com wrote:
I tried building the standalone but ran into a snag.
Here is the error message display when I ran first-setup.sh:
sh ./first-setup.sh --modules=all --engine=luatex --context=current
receiving incremental file
Thanks Mojca. Re-running the command today got me a little further. Thank
you.
The problem encounted now is:
sh ./first-setup.sh --modules=all --engine=luatex --context=current
receiving incremental file list
sent 64 bytes received 322 bytes 85.78
On Thu, Jun 20, 2013 at 6:39 PM, hwit...@gmail.com wrote:
Thanks Mojca. Re-running the command today got me a little further. Thank
you.
The problem encounted now is:
sh ./first-setup.sh --modules=all --engine=luatex --context=current
receiving
