ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [tex-live] difference texlive 2008, 2009
Date: Tue, 16 Feb 2010 12:58:36 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1002161246400.1278@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <hldfkd$raf$1@ger.gmane.org>

On Tue, 16 Feb 2010, Lubos Kolouch wrote:

> Pardon my ignorance, does it mean, I have to run it after every update of
> this package?

You need to run

   source /opt/context-minimals/setuptex

once on each terminal from which you want to run context. If you do not 
use texlive, then you can add this line to your .bashrc (or the rc file of 
whatever shell you use).

setuptex sets PATH so that the minimals binaries are used rather than 
texlive's; setting OSFONTDIR so that you can use system fonts; and setting 
TEXMFCACHE.

> Should that not be part of the install process?

If can be, but that will mean that context-minimals will conflict with 
texlive. With the current approach, you can use both texlive (which is 
needed for latex, texinfo, and plain tex) and context-minimals. All you 
need to do is run

   source /opt/context-minimals/setuptex

once for each terminal session.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-02-16 17:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100108131615.GA2529@nbgentoo.nlcz.cz>
2010-01-09  6:49 ` Taco Hoekwater
2010-01-09  9:05   ` Lubos Kolouch
2010-01-09 10:51     ` Taco Hoekwater
2010-01-10  8:59       ` Lubos Kolouch
2010-01-10  9:01         ` Taco Hoekwater
2010-01-10  9:46         ` Aditya Mahajan
2010-01-13 14:21           ` Lubos Kolouch
2010-01-13 17:02             ` Vedran Miletić
2010-01-13 17:20               ` Lubos Kolouch
2010-01-13 18:15                 ` Vedran Miletić
2010-01-13 18:18             ` Aditya Mahajan
2010-01-13 19:29               ` Lubos Kolouch
2010-02-12  7:29           ` Lubos Kolouch
2010-02-12  7:33             ` Taco Hoekwater
2010-02-12 10:14               ` Lubos Kolouch
2010-02-12 19:54                 ` Aditya Mahajan
2010-02-15 14:12                   ` Lubos Kolouch
2010-02-15 17:29                     ` Aditya Mahajan
2010-02-16  6:57                       ` Lubos Kolouch
2010-02-16 17:58                         ` Aditya Mahajan [this message]
2010-02-12  7:47             ` Aditya Mahajan

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=alpine.LNX.2.01.1002161246400.1278@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).