ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: module sync'ing
Date: Tue, 4 Aug 2009 19:16:09 +0200	[thread overview]
Message-ID: <6faad9f00908041016g25120861v57b5d25f4ddb20aa@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0908041828550.14392@gaston.couberia.bzh>

On Tue, Aug 4, 2009 at 18:32, Peter Münster wrote:
> Hello,
>
> How should module contributions (t-vim, t-french, t-letter, etc.) find
> their way to the minimals today?
>
> (There are so many possibilities, I'm a bit lost:
> modules.contextgarden.net, svn, git, ctan, rsync, email to Mojca, email to
> Hans, and so on... ;)

Aditya has answered you, but just as explanation:

1.) Authors should update modules.contextgarden.net - this is the
primary and definite source (however, I dislike the current interface;
we'll force Patrick to change at least something here, preferrably use
some version control)

2.a) There's a (non-public) mirror of dl.contextgarden.net/modules
that syncs all the modules that should go to CTAN (and renames them at
the same time); CTAN team then syncs automatically once per day. (Read
as: if author updates modules.contextgarden.net, this should
proliferate to CTAN in < 26 hours + one extra day for secondary
mirrors)

2.b) Minimals sync from the same source
(http://minimals.contextgarden.net/current/modules/) at "random"
times.

3.a) TeX Live and MikTeX sync from CTAN automatically (once per day?).

3.b) Users of minimals can use the normal rsync route. Once you use
--extras="t-modulename" it should be updating on regular bases from
that moment on (I just figured out that we currently have no interface
to remove module, but interface needs revision anyway.)

If someone writes a new module someone (me) needs to set up 2.a) and
2.b) to take the new module into account. But of course you may use
whatever way you prefer to fetch your favourite module. You can put it
to texmf-local or texmf-whatever (whatever should not be "context" or
"os-name") or to TEXFHOME (I have a feeling that we have set up that
once, but I'm not 100% sure).

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

  parent reply	other threads:[~2009-08-04 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 16:32 Peter Münster
2009-08-04 16:47 ` Aditya Mahajan
2009-08-04 17:16 ` Mojca Miklavec [this message]
2009-08-04 19:36   ` Peter Münster
2009-08-04 19:59     ` Mojca Miklavec

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=6faad9f00908041016g25120861v57b5d25f4ddb20aa@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).