From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Use latest or current version
Date: Mon, 15 Aug 2011 20:03:13 +0200 [thread overview]
Message-ID: <CALBOmsZcPb7PW-70xVuB1_maCCsoo1WVcMN2FF4PhZhiyi4pHQ@mail.gmail.com> (raw)
In-Reply-To: <CAG-LmmC-gXQtafdrZ8+0dRS4smKPTAUi2=mg1pByr3v0u8Oi_A@mail.gmail.com>
On Mon, Aug 15, 2011 at 19:46, Cecil Westerhof wrote:
> 2011/8/15 Mojca Miklavec wrote:
>>
>> On Mon, Aug 15, 2011 at 19:03, Cecil Westerhof wrote:
>> > I work 'always' with the latest version of ConTeXt. Now a client is
>> > going to
>> > use it. Should I install for them also the latest version, or is it
>> > better
>> > to use the current version (--context=current)?
>>
>> If the latest version works fine, I would install the latest one.
>> "Current is not ready to use yet" :) :) :)
>
> I would expect it the other way around. ;-}
That was the idea, but there are two problems:
- there is no easy way to fix problems in current (and more important:
nobody does it/would do it)
- the whole distribution should be frozen, not just context files (if
modules or binaries or fonts get updated, there may be discrepancies)
I plan to fix that, but that has been on my schedule for over a year already.
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-08-15 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 17:03 Cecil Westerhof
2011-08-15 17:25 ` Mojca Miklavec
2011-08-15 17:46 ` Cecil Westerhof
2011-08-15 18:03 ` 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=CALBOmsZcPb7PW-70xVuB1_maCCsoo1WVcMN2FF4PhZhiyi4pHQ@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).