ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Linux upgrade
Date: Tue, 11 Jul 2006 12:23:12 +0200	[thread overview]
Message-ID: <44B37C10.6020908@elvenkind.com> (raw)
In-Reply-To: <22af238a0607051656i393481bet71ba198fcc373bc2@mail.gmail.com>



gnwiii@gmail.com wrote:
> On 6/23/06, Taco Hoekwater <taco@elvenkind.com> wrote:

>>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.
>>[...]
> 
> 
> This script creates copies of the scripts and has to be run each time
> the scripts are updated.

It does not create copies of any important scripts, it only creates
copies of the stubs that use texmfstart to find the scripts.
There should be no problems with that approach except even if
you forget it occasionally, and it will very likely be added to
ctxtools --update sometime soon, removing the need of post-install
actions completely.

The whole point of texmfstart is that Hans tries to hide kpsewhich
(because it is not present in all distros) and the implementation
language of the actual scripts (because that may change over time).


Greetings, Taco

  reply	other threads:[~2006-07-11 10:23 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
2006-07-05 23:56   ` gnwiii
2006-07-11 10:23     ` Taco Hoekwater [this message]
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=44B37C10.6020908@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).