ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: bb <skip.collins@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: INstalling a new version of context
Date: Mon, 9 May 2005 15:12:00 -0400	[thread overview]
Message-ID: <f03b6a4405050912126516e65@mail.gmail.com> (raw)
In-Reply-To: <427F974F.4060501@elvenkind.com>

[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]

I think I have things working with texlive. I will reproduce the
installation to make sure I capture all steps. It basically comes down
to:

1) Install texlive 2004 to /usr/local/TeX

2) (possibly optional) Compile new pdftex, pdfetex and pdfxtex and
replace executable and pool files in /usr/local/TeX/bin/i386-linux/
and /usr/local/TeX/texmf-local/web2c/ respectively.

3) Install beta cont-tmf.zip into /usr/local/TeX/texmf-context

4) Edit /usr/local/TeX/texmf-local/web2c/texmf.cnf to include the
following modifications from the copy in /usr/local/TeX/texmf/web2c:
TEXMFCONTEXT=$SELFAUTOPARENT/texmf-context
TEXMF={$HOMETEXMF,!!$VARTEXMF,$TEXMFLOCAL,!!$TEXMFCONTEXT,!!$TEXMFMAIN,!!$TEXMFDIST}

5) wget http://www.pragma-ade.com/context/install/linuxtex.zip 
Unzip the file into a temporary directory and cd to tex/texmf-linux/bin.
Copy only the small stub scripts (all less than 50 bytes) to
/usr/local/TeX/bin/i386-linux overwriting similarly named executables.
Copy texmfstart to the same place, again overwriting the existing
executable. Delete the rest of the temporary linuxtex installation.

6) Update /usr/local/TeX/texmf-context/scripts/context/perl/texexec.pl
with the attached patch.

7) Download the latest lm fonts from CTAN and install them in the
correct folders in texmf-context.

8) Run updmap.

9) Run texexec --make --all

I'm sure I have forgotten some crucial step. Corrections and
simplifications are welcome.

On 5/9/05, Taco Hoekwater <taco@elvenkind.com> wrote:
> bb wrote:
> >
> > Reading my own words I see how they don't exactly convey warm
> > appreciation for all the hard work that has been put into context.
> 
> That's ok, i have written stuff in the not so distant past that
> was much, much less appreciative. :-)
> 
> > below. Since texlive 2005 is in the process of being worked out,
> > perhaps a better use of time would be to ensure that a fully
> > functional, up-to-date (and upgradable!) context gets included.
> 
> It wouldn't stay up-to-date for the whole year, only for the first
> six months or so. But you are right that the current (texlive2004)
> situation is particularly messy, and an effort should be made to
> make sure that the next texlive starts off with a more stable
> situation.
> 
> Taco
> 
>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: texexec.pl.patch --]
[-- Type: text/x-patch; name="texexec.pl.patch", Size: 1561 bytes --]

*** /usr/local/TeX/texmf-context/scripts/context/perl/texexec.pl	2005-04-21 18:16:27.000000000 -0400
--- /usr/local/TeX/texmf-local/scripts/context/perl/texexec.pl	2005-05-09 14:39:51.000000000 -0400
***************
*** 2305,2313 ****
          # fall back
          if ($FormatPath eq '') {
              if (($UseEnginePath)&&($EngineDone)) {
!                 $FormatPath = `$kpsewhich --engine=$EnginePath --expand-var=\$TEXFORMATS` ;
              } else {
!                 $FormatPath = `$kpsewhich --expand-var=\$TEXFORMATS` ;
              }
          }
          chomp $FormatPath ;
--- 2305,2313 ----
          # fall back
          if ($FormatPath eq '') {
              if (($UseEnginePath)&&($EngineDone)) {
!                 $FormatPath = `$kpsewhich --engine=$EnginePath --expand-var=\\\$TEXFORMATS` ;
              } else {
!                 $FormatPath = `$kpsewhich --expand-var=\\\$TEXFORMATS` ;
              }
          }
          chomp $FormatPath ;
***************
*** 2474,2480 ****
          $texformats = '' ;
      }
      if ($texformats eq '') {
!         $texformats = `kpsewhich --expand-var=\$TEXFORMATS`.chomp ;
      }
      if ($texformats !~ /web2c[\/\\].*\$ENGINE/) {
          $texformats =~ s/web2c/web2c\/{\$ENGINE,}/ ;
--- 2474,2481 ----
          $texformats = '' ;
      }
      if ($texformats eq '') {
!         $texformats = `kpsewhich --expand-var=\\\$TEXFORMATS` ;
!         chomp($texformats) ;
      }
      if ($texformats !~ /web2c[\/\\].*\$ENGINE/) {
          $texformats =~ s/web2c/web2c\/{\$ENGINE,}/ ;

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2005-05-09 19:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050508100002.AAEAA127B3@ronja.ntg.nl>
2005-05-09  3:01 ` bb
2005-05-09  9:18   ` Taco Hoekwater
2005-05-09 15:45     ` bb
2005-05-09 17:01       ` Taco Hoekwater
2005-05-09 19:12         ` bb [this message]
2005-05-10 12:45           ` texexec.pl patch bb
2005-05-09 20:21       ` INstalling a new version of context Hans Hagen
2005-05-07 18:01 olibou
2005-05-07 20:29 ` John R. Culleton
2005-05-08  8:18   ` olibou
2005-05-08 20:40   ` Hans Hagen
2005-05-08 20:44 ` Hans Hagen
2005-05-09 10:24   ` John R. Culleton

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=f03b6a4405050912126516e65@mail.gmail.com \
    --to=skip.collins@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=skip@interbit.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).