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>
Cc: Yatskovsky <yatskovsky@gmail.com>
Subject: Re: mtx-update --context=beta?
Date: Wed, 16 Apr 2008 20:44:12 +0200	[thread overview]
Message-ID: <6faad9f00804161144l755ece75head01d86dc48af03@mail.gmail.com> (raw)
In-Reply-To: <7871fcf50804161019p7ec82e18ha4aff6c4e5af7cd5@mail.gmail.com>

On Wed, Apr 16, 2008 at 7:19 PM, Joel C. Salomon wrote:
> I'm putting together my own rsync calls based on the Minimals
>  firstsetup.bat and Vyatcheslav's installer.  Found a difference:
>  firstsetup.bat includes the switch --context=beta in its call to
>  mtx-update.  What is the difference if it's used or no?

Hello Joel,

I have added that switch after Vyatcheslav has created his installer
(and forgot to ask him to support the switch in his GUI).
Vyatcheslav, I hope that you're reading this :)

Hans uploads "current" and "beta" releases on his web page (sometimes
also alpha, but not very often).
    http://www.pragma-ade.com/download-1.htm
    http://www.pragma-ade.com/download-2.htm
Beta versions mean: "I have put some experimental stuff there - dear
users, please test and tell me if it works OK. If nobody complains for
several days or weeks, this will become a curren/stable release".

--context=beta means that it will sync with either beta (if one
exists) or current (if there is no beta). Default is
--context=current.

See also
   http://minimals.contextgarden.net/current/context/
You can also say --context=2008.01.11, but I have no idea whether
there is/will be space to store all of the distributions (I need to
move the files to Taco's server first).

By writing your own calls I meant even circumventing mtx-update (it
doesn't do anything really clever) and write rsync calls directly. If
you do that, you will have full control of what not to include (you
might want not to include fonts/other for example).

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
___________________________________________________________________________________


      reply	other threads:[~2008-04-16 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 17:19 Joel C. Salomon
2008-04-16 18:44 ` 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=6faad9f00804161144l755ece75head01d86dc48af03@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=yatskovsky@gmail.com \
    /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).