From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Moving module installation from first-setup.sh to ctxtools
Date: Wed, 1 Jun 2011 08:53:15 +0200 [thread overview]
Message-ID: <BANLkTim+7n3wa7QyYy6Bv-=D9oGbdj9=Uw@mail.gmail.com> (raw)
In-Reply-To: <loom.20110601T011210-594@post.gmane.org>
On Wed, Jun 1, 2011 at 01:15, Bruce <bdarcus.lists@gmail.com> wrote:
> Mojca Miklavec <mojca.miklavec.lists <at> gmail.com> writes:
>
>
> [snip]
>
>> One more thing: are you talking about TL 2010 or TL 2011?
>
> I had installed 2010, but am now upgrading.
>
>> In case that you are talking about TL 2011, you can fetch files from
>> http://ctan.ijs.si/mirror/tlpretest/ or wait for other servers to
>> recover from yesterday's problem.
>>
>> It is also not too advisable to use ctxtools to update ConTeXt in TeX
>> Live (or at least you must know what you are doing and be prepared for
>> potential problems).
>
> So is the code in the texlive repositories updated frequently enough that this
> isn't a problem WRT to ConTeXt: that I can just let tlmgr handle it?
The modules in TeX Live are updates in sync with all the rest.
The only difference is that the main CTAN server only syncs once per
day (which might add +1 day), that TeX Live repositories are being
rebuilt only once per day (another +1 day in worst case) and worst
case +1 day that your mirror syncs with CTAN.
The reason why ConTeXt is not updated is that ConTeXt requires the
latest version of LuaTeX which is often a problem. If modules break
compatibility with slightly older ConTeXt version, it is author's
responsibility, but modules develop much more slowly than ConTeXt, so
this is rarely a problem. There is one single module written for MKVI
that is in minimals, but didn't go to CTAN exactly for the reason that
ConTeXt MKVI develops way too fast and module could not keep
up/version of ConTeXt in TL would be way out of date anyway.
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-06-01 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 16:26 Bruce
2011-05-31 16:37 ` Mojca Miklavec
2011-05-31 16:44 ` Bruce
2011-05-31 16:52 ` Mojca Miklavec
2011-05-31 21:17 ` Bruce
2011-05-31 21:26 ` Mojca Miklavec
2011-05-31 21:30 ` Mojca Miklavec
2011-05-31 23:15 ` Bruce
2011-06-01 6:53 ` Mojca Miklavec [this message]
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='BANLkTim+7n3wa7QyYy6Bv-=D9oGbdj9=Uw@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.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).