From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: location of old ConTeXt versions?
Date: Tue, 10 Nov 2015 14:33:58 +0100 [thread overview]
Message-ID: <CALBOmsYazox4qp7JaRrdoGbkqhT9OH25C8S9-c9L8xoa8AH2jQ@mail.gmail.com> (raw)
In-Reply-To: <871tby80rt.fsf@insight.mit.edu>
On Tue, Nov 10, 2015 at 2:03 PM, Sanjoy Mahajan <sanjoy@mit.edu> wrote:
> Dear ConTeXters,
>
> In order to correct an embarrassing thinko (wrong units of
> acceleration!) in my book for its next printing, I need to regenerate
> the PDF changing only that one spot.
>
> Thus, I am looking for an old ConTeXt version, 2014.05.17. The latest
> versions find different page and line breaks. I haven't been able to
> convince them to rediscover the old breaks (which were carefully
> optimized over a few miserable weeks back in 2014).
>
> I have the 2014.05.17 minimal on my old laptop, a i386 32-bit Linux
> laptop (2006 vintage). I joined the 2010 decade recently and now use
> 64-bit laptop; the 32-bit minimals don't work on it.
>
> The wiki, at
> <http://wiki.contextgarden.net/ConTeXt_Standalone#Reverting_to_an_older_installation>,
> says that the old versions are available at
> <http://minimals.contextgarden.net/current/context/>, where I found only
> the latest versions.
>
> Could you point me to a linux/64-bit minimal for 2014.05.17? I'll
> update the wiki accordingly. (If the old versions are gone, I'll dig out
> my old laptop and regenerate it that way, or try convincing the laptop
> to use 32-bit executables as well.)
This is slightly suboptimal at the moment.
My suggestion would be the following:
- fetch the latest minimals for 64-bit linux
- remove texmf-context and replace it with the one from your old
machine (alternatively you could fetch that version of ConTeXt from
GIT)
- check which version of LuaTeX you have on the old 32-bit box (it's
probably beta-0.79.1)
- fetch that version from SVN from
http://svn.contextgarden.net/suite-bin/tex/x86_64-linux
(if it's that version, just checkout r197)
- you might need to replace mtxrun from the old version (or maybe I
forgot another thing or two)
Everything else should keep working unless some font names changed in
the meantime.
Alternatively start with your old 32-bit tree and just add the
texmf-linux-64 tree from the new installation to it (of course make
sure to replace luatex and potentially other scripts in that tree).
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-11-10 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 13:03 Sanjoy Mahajan
2015-11-10 13:33 ` Mojca Miklavec [this message]
2015-11-10 17:02 ` Sanjoy Mahajan
2015-11-10 17:21 ` luigi scarso
2015-11-10 18:19 ` Sanjoy Mahajan
2015-11-10 18:57 ` luigi scarso
2015-11-10 13:58 ` Peter Münster
2015-11-10 17:04 ` Sanjoy Mahajan
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=CALBOmsYazox4qp7JaRrdoGbkqhT9OH25C8S9-c9L8xoa8AH2jQ@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).