From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: updates without rsync
Date: Thu, 28 May 2009 11:27:34 +0200 [thread overview]
Message-ID: <4A1E5906.2050600@wxs.nl> (raw)
In-Reply-To: <OF5255F523.8E75EB73-ON802575C4.002AFC27-802575C4.002E192E@converteam.com>
richard.stephens@converteam.com wrote:
> Gentlemen and Ladies,
>
> I am using ConTeXt on a company Windows PC behind two firewalls with no
> possibility of accessing or changing the firewalls. I've tried to update
> using the minimals installation and rsync, but nothing gets through. What
> is the recommended method of updating to the latest ConTeXt when rsync is
> not an option?
>
> The last time I tried, I downloaded cont-tmf.zip from
> http://www.pragma-ade.com/download-1.htm and unzipped the contents to
> overwrite everything in texmf-local. Is this still the best way?
should work ok
- unzip in relevant tree
- mktexlsr
- luatools --generate
- luatools --selfupdate
- mtxrun --selfupdate
- texexec --make (for mkii)
- context --make (for mkiv)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-28 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 8:23 richard.stephens
2009-05-28 9:27 ` Hans Hagen [this message]
2009-05-28 18:33 ` Mojca Miklavec
2009-05-28 19:36 ` Mojca Miklavec
2009-05-28 23:32 ` Alan BRASLAU
2009-05-29 13:04 ` Peter Münster
2009-05-29 16:07 ` Diego Depaoli
2009-05-30 9:17 ` Mojca Miklavec
2009-05-30 17:17 ` Diego Depaoli
[not found] <6faad9f00905281209u2932c88ct1290a543e95c49e7@mail.gmail.com>
2009-05-29 9:25 ` richard.stephens
2009-05-29 10:34 ` Hans Hagen
[not found] <a09128560905290304r3adf9ae6p1432b88a6c2968c6@mail.gmail.com>
2009-05-29 13:12 ` richard.stephens
2009-05-29 13:22 ` Peter Rolf
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=4A1E5906.2050600@wxs.nl \
--to=pragma@wxs.nl \
--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).