From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Linux upgrade
Date: Fri, 23 Jun 2006 10:44:18 +0200 [thread overview]
Message-ID: <449BA9E2.60306@elvenkind.com> (raw)
In-Reply-To: <200606221918.07473.john@wexfordpress.com>
John R. Culleton wrote:
>
> Let me start all over. Assuming a working TeX installation
> (either tetex or texlive 2005) what incantation must I perform to
I think it is slighty better to start with TeXLive than with
teTeX because it is a bit newer so you do not have to update
as much, but you may prefer to keep your teTeX.
> upgrade to the latest stable Context and what specific zip file
> should I use?
The wiki is a bit out of date, but there is a complete page on Linux
installations: http://wiki.contextgarden.net/Linux_Installation
After following those instructions, everything should be ok except
for the new ruby script links and texmfstart's warning. For
that, do the following:
* make sure you have ruby installed. If not, do that first
* go to the scripts/context/stubs/unix/ directory in your
freshly unpacked ConTeXt distribution, make sure you
have write permissions to the TeX binaries directory,
and run something like the shell script that follows.
I turned on the interaction of rm and cp, but there are
NO GUARANTEES!
My skill in shell programming is pretty awful.
Cheers, Taco
#!/bin/sh
TEXMFBIN=`which texexec`
TEXMFBIN=`dirname $TEXMFBIN`
if [ -f $TEXMFBIN/texmfstart ]; then
rm -i $TEXMFBIN/texmfstart
fi
cp -i ../../ruby/texmfstart.rb $TEXMFBIN/texmfstart
chmod a+x $TEXMFBIN/texmfstart
for a in *; do
TEST=`which $a`;
echo $TEST;
if [ $TEST ] ; then
rm -i $TEST
fi;
chmod a+x $a
cp -i $a $TEXMFBIN
done;
next prev parent reply other threads:[~2006-06-23 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 23:18 John R. Culleton
2006-06-23 1:37 ` Aditya Mahajan
2006-06-23 14:17 ` John R. Culleton
2006-06-23 15:54 ` Aditya Mahajan
2006-06-23 17:19 ` Hans Hagen
2006-07-05 14:25 ` Aditya Mahajan
2006-06-23 8:44 ` Taco Hoekwater [this message]
2006-07-05 23:56 ` gnwiii
2006-07-11 10:23 ` Taco Hoekwater
2006-06-23 9:39 ` luigi scarso
2006-06-23 16:34 ` Peter Münster
2006-06-23 22:00 ` John R. Culleton
2006-06-23 22:48 ` John R. Culleton
2006-06-24 7:46 ` Peter Münster
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=449BA9E2.60306@elvenkind.com \
--to=taco@elvenkind.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).