ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: location of old ConTeXt versions?
Date: Tue, 10 Nov 2015 18:21:28 +0100	[thread overview]
Message-ID: <CAG5iGsB=tWM9H3C=fa=VEDOK_yDBiUPa_XD4PNZ5r8UZa3ew3g@mail.gmail.com> (raw)
In-Reply-To: <87k2pp7pom.fsf@insight.mit.edu>


[-- Attachment #1.1: Type: text/plain, Size: 1859 bytes --]

On Tue, Nov 10, 2015 at 6:02 PM, Sanjoy Mahajan <sanjoy@mit.edu> wrote:

> Thanks, Mojca.  Inspired by your suggestions, I did the following (which
> should work on Ubuntu too, but I am using Debian testing
> a.k.a. stretch):
>
> $ dpkg --add-architecture i386
> $ apt update
> $ apt install libc6-i386
>
> and voila my old binaries from the minimal worked!
>
> There were other issues that aren't so easy to solve:
>
> 1. asymptote meanwhile is at version 2.35 instead of 2.31, which affects
>    figure sizes slightly.
>
> 2. graphviz and dot (for all the tree diagrams) were at version 2.26 and
>    are now at 2.28, which affects figure sizes somewhat and their layout
>    slightly.
>
> 3. Inkscape was 0.48 and is now 0.91.  That affected the conversion from
>    svg to eps of one figure.  That I worked around by just using the
>    previously converted eps figure instead of the svg.
>
> All the changes above can affect the page and line breaks, but I tweaked
> a bit until that didn't happen.
>
> It does show a general problem with large complex documents regarding
> software versions.  ConTeXt is the fastest-changing component, but the
> other components also change, and one needs a way to preserve the entire
> software stack.
>
> That's a software-engineering problem, and maybe others have found
> solutions?
>
> My first book (_Street-Fighting Mathematics_) is frozen with its typos
> because I cannot reproduce its stack at all, so all the new printings
> get the old typos.  Through bad luck, at the time (2009) I happened to
> have a never-released version of the tex fonts, now long overwritten by
> proper versions, and I also didn't use a ConTeXt minimal back then, so I
> don't have the other binaries and TeX in the right form.
>
>


Have you seen this site ?

http://ftp.math.utah.edu/pub/tex/historic/systems/texlive/

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2637 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2015-11-10 17:21 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
2015-11-10 17:02   ` Sanjoy Mahajan
2015-11-10 17:21     ` luigi scarso [this message]
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='CAG5iGsB=tWM9H3C=fa=VEDOK_yDBiUPa_XD4PNZ5r8UZa3ew3g@mail.gmail.com' \
    --to=luigi.scarso@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).