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: Is Minimals ready for non-developers to use? (Tom)
Date: Mon, 14 Mar 2011 19:55:40 +0100	[thread overview]
Message-ID: <AANLkTin8TFC3Ww39c1bnP-cSo-oHcmPpNK_FzRoUnQzY@mail.gmail.com> (raw)
In-Reply-To: <000401cbe24a$ea2b3ab0$be81b010$@com>

On Mon, Mar 14, 2011 at 14:22, Tom wrote:
> Dalyoung,
>
> To the contrary, You have been most helpful. Installing the latest version
> of Minimals worked fine but I wonder why they even advertise that there is a
> stable version to be downloaded.

When minimals were created, a new "stable" version was released
approximately once a week. It used to be a problem to get the beta
version working since beta often depended on a new version of luatex
(which was also released every two/three weeks, but often not
synchronized with ConTeXt releases).

Now Hans only releases a stable version twice a year or so. The
problem is that minimals have not been designed with that in mind and
there is only a single version of texmfcnf.lua and only a single
version of luatex binary. Consequently minimals can only work either
with beta or with current when the two versions diverge, but not with
both and beta has priority.

I need to change the way the distribution works entirely, from the
grounds up (I have many parts ready, but not ready to publish yet).

An easy solution would be to create another mirror and only provide a
working current version there.

> I guess they mean a stable version of MKII.
> I had the same experience that you had with the Introduction not showing up
> in the TOC. Do you know how to report a bug?

You don't need to report it. I'm aware of that flaw. I could do a
temporary fix, but I would prefer to fix it properly. I'm sorry that
it alredy took me several years to address those issues, but I promise
to fix it before the conference. Properly.

You also need to keep in mind that even though it is advertized as
stable, bugs won't be fixed (many project often have at least two
branches of development - one for fixing the released version and one
for real development; the released version should get bugfixes, but in
context development that doesn't and won't happen unless some
volunteer starts carefully checking the new code and only applies
bugfixes to the stable version).

So most people that use ConTeXt actively need bugfixes very often and
the only way to get the bugs fixed is to use the latest version. Well,
latest version comes with its own bugs, but at least you have a chance
to get them fixed quickly.

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
___________________________________________________________________________________


  reply	other threads:[~2011-03-14 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1401.1300033032.4223.ntg-context@ntg.nl>
2011-03-14  9:16 ` Jeong Dalyoung
2011-03-14 13:22   ` Tom
2011-03-14 18:55     ` Mojca Miklavec [this message]
2011-03-14 20:10 Tom
2011-03-14 20:17 ` 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=AANLkTin8TFC3Ww39c1bnP-cSo-oHcmPpNK_FzRoUnQzY@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).