From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: distro info
Date: Mon, 30 Jun 2008 09:03:18 +0200 [thread overview]
Message-ID: <326847810806300003n3da3499ey1e09216ec705d443@mail.gmail.com> (raw)
In-Reply-To: <m2k5g74hm2.fsf@stanford.edu>
[-- Attachment #1.1: Type: text/plain, Size: 3103 bytes --]
Hi Jesse,
> 1. What's the difference between getting the texmf tree using rsync, as
> you suggest, and using ctxtools --updatecontext? Are those equivalent?
You might read the underneath thread from here on, as well as its later
posts...
http://archive.contextgarden.net/message/20080620.070341.aca1fbd9.en.html
Maybe this short one also...
http://archive.contextgarden.net/message/20080621.153103.9fcfc856.en.html
Hope this helps,
Alan
On Mon, Jun 30, 2008 at 7:27 AM, Jesse Alama <alama@stanford.edu> wrote:
> "Mojca Miklavec" <mojca.miklavec.lists@gmail.com> writes:
>
>> On Sat, Jun 14, 2008 at 6:35 PM, Jesse Alama wrote:
>>> "Thomas A. Schmitz" writes:
>>>
>>> The basis for my own comments in this thread do not lie in a preference
>>> for graphical tools, but rather for a straightforward way to stay
>>> up-to-date with the whole of ConTeXt in a way that ctxtools does not
>>> currently provide. A command-line interface for that would be great,
>>> and so would a graphical tool.
>>
>> That's not a general solution, but if you need it for yourself, you
>> can put the following to some file and execute it whenever you want:
>>
>> rsync -av rsync://contextgarden.net/minimals/current/context/beta/
>> /path/to/your/texmf/
>> rsync -av rsync://
contextgarden.net/minimals/current/bin/luatex/linux/bin/
>> /path/to/your/binaries/
>> etc.
>>
>> There's a limited set of folders that you need to update, and it will
>> only update new files, you don't need to update everything.
>
> Two questions:
>
> 1. What's the difference between getting the texmf tree using rsync, as
> you suggest, and using ctxtools --updatecontext? Are those equivalent?
>
> 2. It looks like the subdirectories that I want are
>
> common
> context
> luatex
> man
> metapost
>
> if I want to follow only luatex development. (The only subdirectories
> that aren't in that list are mswin, which doesn't apply to me, and
> pdftex and xetex.) I'd like to just put this on top of my TeXLive
> (2007) distribution. Once I copy thse binaries to my TeXLive binary
> directory, what's the next step? Do I need to rebuild the ConTeXt
> format, for example?
>
> What I'm looking for is a way to keep up-to-date with ConTeXt and LuaTeX
> development; I'd rather not keep a separate installation with all and
> only ConTeXt in it, together with a shell script that sets up *only*
> ConTeXt. I'm happy to keep up-to-date by overwriting the relevant parts
> of my TeXLive distribution with the freshest texmf and binaries. That
> way, within a single shell I can use the freshest ConTeXt as well as
> LaTeX and pacakges from the TeX Collection. Perhaps I am going against
> the intention of the "minimal installation"; but the discussion of how
> to get a minimal ConTeXt installation overlaps with the discussion of
> how to stay up-to-date. I'm more interested in the latter than the
> former. Perhaps the best thing for such a user would be to just track
> the TeXLive development tree using cvs or rsync. I'm curious to hear
> any suggetions.
>
> Thanks,
>
> Jesse
>
> --
> Jesse Alama (alama@stanford.edu)
[-- Attachment #1.2: Type: text/html, Size: 4406 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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-30 7:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 14:36 Andrea Valle
2008-06-10 14:43 ` Andrea Valle
2008-06-10 15:29 ` Wolfgang Schuster
2008-06-10 15:30 ` Otared Kavian
2008-06-10 15:34 ` Hans Hagen
2008-06-10 17:21 ` David
2008-06-10 17:37 ` Hans Hagen
2008-06-10 20:31 ` Andrea Valle
2008-06-12 1:22 ` David
2008-06-12 7:51 ` Olivier Guéry
2008-06-12 8:58 ` Mojca Miklavec
2008-06-10 15:58 ` Mojca Miklavec
2008-06-10 20:27 ` Andrea Valle
2008-06-10 21:08 ` Mojca Miklavec
2008-06-11 12:09 ` Oliver Buerschaper
2008-06-11 14:55 ` Andrea Valle
2008-06-11 16:05 ` Mojca Miklavec
2008-06-11 16:55 ` Andrea Valle
2008-06-11 20:43 ` Jesse Alama
2008-06-12 9:00 ` Andrea Valle
2008-06-13 16:40 ` Henning Hraban Ramm
2008-06-13 17:08 ` Andrea Valle
2008-06-13 18:01 ` Mojca Miklavec
2008-06-13 18:20 ` Henning Hraban Ramm
2008-06-13 18:26 ` Matthias Weber
2008-06-13 19:23 ` Henning Hraban Ramm
2008-06-13 17:57 ` Thomas A. Schmitz
2008-06-14 11:07 ` Oliver Buerschaper
2008-06-14 11:35 ` Thomas A. Schmitz
2008-06-14 13:57 ` Andrea Valle
2008-06-14 17:36 ` Thomas A. Schmitz
2008-06-14 21:38 ` Henning Hraban Ramm
2008-06-14 23:32 ` Charles P. Schaum
2008-06-14 14:19 ` Oliver Buerschaper
2008-06-14 16:35 ` Jesse Alama
2008-06-14 18:59 ` Mojca Miklavec
2008-06-14 23:05 ` Diego Depaoli
2008-06-15 0:41 ` Charles P. Schaum
2008-06-15 1:36 ` Matthias Weber
2008-06-15 9:40 ` Andrea Valle
2008-06-30 5:27 ` Jesse Alama
2008-06-30 7:03 ` Alan Stone [this message]
2008-06-30 8:20 ` Mojca Miklavec
2008-06-30 16:21 ` George N. White III
2008-06-14 11:48 ` Andrea Valle
2008-06-14 13:55 ` John Culleton
2008-06-17 16:02 ` searchable pdf in mkii, usepdffontresource stub Oleg Kolosov
2008-06-17 16:34 ` Hans Hagen
2008-06-17 18:55 ` Oleg Kolosov
2008-06-17 19:13 ` Hans Hagen
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=326847810806300003n3da3499ey1e09216ec705d443@mail.gmail.com \
--to=software.list.1es9s@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).