From: hwitloc@gmail.com
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Problem with Standalone
Date: Thu, 16 Jan 2014 18:23:23 +0900 [thread overview]
Message-ID: <20140116182323.1680@binki> (raw)
In-Reply-To: Your message of Wed, 15 Jan 2014 13:39:36 +0100 <52D68188.8070209@wxs.nl>
Hans Hagen <pragma@wxs.nl> wrote:
> On 1/15/2014 12:06 PM, hwitloc@gmail.com wrote:
> >
> > Hans Hagen <pragma@wxs.nl> wrote:
> >
> >> On 1/15/2014 7:56 AM, hwitloc@gmail.com wrote:
> >>>
> >>>
> >>>>
> >>>> I am trying to load the standalone but have ran into a problem.
> >>>>
> >>>> Platform: cygwin on Windows XP
> >>>>
> >>>> Here is what I did to try to get it all loaded and setup:
> >>>>
> >>>> #1 rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh .
> >>>> sh ./first-setup.sh || exit 3
> >>>>
> >>>> The following files are loaded:
> >>>> receiving incremental file list
> >>>> bin/
> >>>> bin/cygiconv-2.dll
> >>>> bin/cygwin1.dll
> >>>> bin/kpathsea620.dll
> >>>> bin/lua52.dll
> >>>> bin/luatex.dll
> >>>> bin/mtx-update.lua
> >>>> bin/mtxrun.dll
> >>>> bin/mtxrun.exe
> >>>> bin/mtxrun.lua
> >>>> bin/rsync.exe
> >>>> bin/texlua.exe
> >>>>
> >>>>
> >>> The above only populated /opt/context/bin
> >>>
> >>>
> >>>
> >>>> Re: When you want to use context, you need to initialize the tree by typing:
> >>>> . /opt/context/tex/setuptex
> >>>>
> >>>> NOTE: there is no /opt/context/!! It doesn't get loaded.
> >>>
> >>> I mean there is no /opt/context/tex so no /opt/context/tex/setuptex..
> >>>
> >>>
> >>>>
> >>>> Any ideas of what is wrong? Any work around to get the proper tex directory contents?
> >>>
> >>> Any suggestions are apprecaited.
> >>
> >> can you run ./firstsetup ?
> >>
> >
> > ../firstsetup.sh was ran and it was first setup that created and populated the bin directory. But nothing was done for a tex directory.
>
> then you need to figure out why it failed ... messages and so
> ... maybe an rsync issue (you can try to add prints to mtx-update.lua
> (but then also comment the first rsync in firstsetup so that it
> doesn't get overwritten)
Yes I am trying to find out. That's why I sent the message in the first place.
I will endeaver to find out more inforation.
Is there a way to download a three without using rsync? Perhaps a tarball or other archive format?
Regards
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-01-16 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 5:17 Henman
2014-01-15 6:56 ` hwitloc
2014-01-15 9:05 ` Hans Hagen
2014-01-15 11:06 ` hwitloc
2014-01-15 12:39 ` Hans Hagen
2014-01-16 9:23 ` hwitloc [this message]
2014-01-16 16:29 ` Hans Hagen
2014-01-15 13:47 ` Mojca Miklavec
2014-01-16 9:20 ` hwitloc
2014-01-16 10:34 ` Mojca Miklavec
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=20140116182323.1680@binki \
--to=hwitloc@gmail.com \
--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).