From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Geeze, I might try Linux after all... (not too off-tpic I hope)
Date: Fri, 20 Jun 2008 17:05:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0806201644490.15533@nqv-yncgbc> (raw)
In-Reply-To: <326847810806200921p1af4ca96l8f7442b810a5092f@mail.gmail.com>
On Fri, 20 Jun 2008, Alan Stone wrote:
> Thanks Mojca.
>
>> If you are lucky, it puts the files where you want them to be, but
>> since every installation works its own way, it's hard to predict where
>> to put them;
>> ...
>> Of course you can. But if you happen to update TL package, your
>> additions will be destroyed. And you need to rebuild all the other
>> formats. It's not so harmful.
>>
>> Supposed to relates to "your system would be supposed to update its
>> own packages", but for ConTeXt it obviously doesn't do.
>> ...
>> If you destroy (overwrite) the old binary :) - if you dowload the
>> wrong binary, then you have neither working. Generally, it should work
>> OK.
>
> Caramba! Tricky, tricky stuff.
>
> FYI, http://wiki.contextgarden.net/Installation_hints mentions, under the
> "Updating" paragraph, (after calling ctxtools --updatecontext) "then you
> have to regenerate the format(s)...", while you wrote
>
>> All it does is:
>> - download the zip
>> - unzip it
>> - make the formats
>
> I wonder, for the record, ...
>
> Is there any (installation) process which enables ctxtools to update ConTeXt
> without risking to #@!&X% it up ?
Yes. If you do not need latex, the safest thing to not install anything
tex related from your distribution and only install the minimals from the
garden. (You need to update using the mechanism provided by the minimals,
and not ctxtools).
The trouble with this is two-fold. First, you may need to use latex, and
second, many packages on linux require tex, so you get a tex from the
distribution also.
Now you have two options: Either isolate minimal context from the one
provided by the distribution, or make them co-exist. Isolating them is
easy, the minimals even come with a script "setuptex" which does that. So,
you just source setuptex before running context. If you want minimals and
distribution tex to coexits, things are a bit tricky. You need to
understand how the tex distribution works, which is an intangled (for the
want of a better word) mess.
However, the more fundamental question is: why do you need to update tex
manually, why doesn't the distribution update tex frequently. Part of the
reason is that it did not need to. Before luatex and xetex, tex binaries
got updated occasionally. So, a periodic update of the binaries was good
enough. As for macro packages, the biggest component is LaTeX, and LaTeX
core is updated *very* slowly. So, again a periodic update was good
enough.
ConTeXt somehow spoils the party by adding features at an alarmingly fast
rate. So, if you want to use new features you must update. So, someone
needs to package everything for the distribution so that all users can
frequently update context.
Currently the only distribution that does that is Debian. Norbert Preining
maintains a .deb for context macros which is updated fairly regularly. So,
if you are on a debian based system, you can use Norbert's context
package, and have a fairly recent context (~1-2 months old) distribution.
For most cases this would work, unless you want to test the latest
features.
> Side-question: "But if you happen to update TL package" - what does TL
> stand for ?
Texlive. Currently TUG (Tex User group) releases a DVD each year
containing the recent copy of all tex/latex/context packages and all
binaries needed to run tex and friends on Windows, linux and mac. These
days, most linux distributions use texlive as a source of tex packages
that they include.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-20 21:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 10:28 Alan Stone
[not found] ` <326847810806130328k73f9ed0bw4ec3ede296a29d55@mail.gmail.co m>
2008-06-13 10:42 ` Alan Stone
2008-06-13 12:09 ` luigi scarso
2008-06-13 12:38 ` Michael Hallgren
2008-06-13 13:07 ` Diego Depaoli
2008-06-13 12:53 ` Olivier Guéry
2008-06-13 13:37 ` Charles P. Schaum
2008-06-13 14:53 ` John Devereux
2008-06-14 6:20 ` Alan Stone
2008-06-14 7:29 ` Alan Stone
2008-06-14 7:40 ` Taco Hoekwater
2008-06-14 9:07 ` luigi scarso
2008-06-14 9:38 ` Matija Šuklje
2008-06-14 11:25 ` John Culleton
2008-06-19 19:40 ` Alan Stone
2008-06-20 6:37 ` Wolfgang Schuster
2008-06-20 6:45 ` Alan Stone
2008-06-20 7:03 ` Mojca Miklavec
2008-06-20 8:17 ` Alan Stone
2008-06-20 12:21 ` Alan Stone
2008-06-20 12:27 ` Wolfgang Schuster
2008-06-20 13:39 ` Alan Stone
2008-06-20 14:31 ` Mojca Miklavec
2008-06-20 16:21 ` Alan Stone
2008-06-20 21:05 ` Aditya Mahajan [this message]
2008-06-21 7:44 ` Alan Stone
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.1.00.0806201644490.15533@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).