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: Keeping up-to-date under TeXLive
Date: Fri, 21 Dec 2007 21:17:24 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.0.9999.0712212108050.10153@nqv-yncgbc> (raw)
In-Reply-To: <7871fcf50712210922i75dbcda9r7aa2f5efe142e941@mail.gmail.com>

On Fri, 21 Dec 2007, Joel C. Salomon wrote:

> My new Ubuntu installation includes TeXLive version 2007-10.  Is there
> a way for me to keep the ConTeXt part of this up-to-date with current
> (stable) versions?

I am in the same situation. Ubuntu 7.10, but the context version of the 
latest texlive is too old for my needs.

> Considering that I have XeTeX 0.996, do I want to,
> or should I stick with what currently works?

In most cases (except if you want to test mkiv) the current binaries are 
ok. So, for pdftex (1.40.3-2.2), metapost (0.993) and xetex (0.996), I 
stick with the version provided by ubuntu. So far I have not run into a 
bug that was fixed in a higher version. If I do, I will download the 
latest binaries.

For me, the more important thing is to have an uptodate context files. 
After a bit of trial and error, this is what I settled on.

Create $HOME/texmf. Download justtex.zip, and cont-tmf.zip, cont-fnt.zip 
from pragma's website, and unzip them inside $HOME/texmf. Download the 
font files from TeX Gyre and unzip then in $HOME/texmf.

Remake the formats, move the stubs and few programs to the path, and you 
are done.

The only drawback of this is that you have to update manually. ctxtools 
--updatecontext unzip the file in TEXMFLOCAL, and not TEXMFHOME, so it 
does not work with this setup.

I used $HOME/texmf rather than TEXMFLOCAL because there are some other 
programs that install stuff at TEXMFLOCAL. With the current mechanism, I 
can just mv $HOME/texmf to another directory, and go back to the context 
that comes with unbuntu.

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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2007-12-22  2:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 17:22 Joel C. Salomon
2007-12-21 17:59 ` luigi scarso
2007-12-21 23:42 ` Mojca Miklavec
2007-12-22  2:17 ` Aditya Mahajan [this message]
2007-12-23  3:47   ` Joel C. Salomon
2007-12-23 10:08     ` Mojca Miklavec
2007-12-26  0:56       ` Joel C. Salomon
2007-12-26 11:14         ` Mojca Miklavec
2007-12-26 16:12           ` Ciro Soto
2007-12-26 19:14             ` Aditya Mahajan
2007-12-26 19:15           ` Aditya Mahajan
2007-12-23 15:06     ` Aditya Mahajan
2007-12-22 15:05 ` 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=alpine.DEB.0.9999.0712212108050.10153@nqv-yncgbc \
    --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).