From: "John R. Culleton" <john@wexfordpress.com>
Subject: Re: Linux upgrade
Date: Fri, 23 Jun 2006 10:17:17 -0400 [thread overview]
Message-ID: <200606231017.17609.john@wexfordpress.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0606222135410.2420@nqvgln>
On Thursday 22 June 2006 09:37 pm, Aditya Mahajan wrote:
> Hi John,
> Others will be able to tell you better on how to upgrade on Linux (I
> myself use windows) but
>
> > standard /usr/share/texmf tree. No joy. I get messages telling me to use
> > the texmfstart command instead. This is as I recall a Windows thingie.
>
> you need texmfstart on linux also. Does everything work fine if you
> use texmfstart?
>
> Aditya
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
Not yet. I am unsure what texmfstart is supposed to do. It is a
Ruby script. Does it replace texexec or does it manage texexec?
Anyhow back to the starting line. I have reinstalled the version
of tetex that comes with Slackware 10.2 so at least I am
operational. I have in addition downloaded the iso's for
slackware-current. I tried upgrading just the TeX part of
Slackware but there are too many differences in libraries between
Slack 10.2 and Slack current.
For my next step I will install Slack-current on a spare
partition. Then I will test Context there and note the version.
If it is fairly recent then I will proceed using that partition.
If not, then I may experiment with the many and various
suggestions for upgrading.
My thanks to all who replied. I am hanging in there. Someday I
will get the upgrade going, but probably not today.
--
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf
Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf
next prev parent reply other threads:[~2006-06-23 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 23:18 John R. Culleton
2006-06-23 1:37 ` Aditya Mahajan
2006-06-23 14:17 ` John R. Culleton [this message]
2006-06-23 15:54 ` Aditya Mahajan
2006-06-23 17:19 ` Hans Hagen
2006-07-05 14:25 ` Aditya Mahajan
2006-06-23 8:44 ` Taco Hoekwater
2006-07-05 23:56 ` gnwiii
2006-07-11 10:23 ` Taco Hoekwater
2006-06-23 9:39 ` luigi scarso
2006-06-23 16:34 ` Peter Münster
2006-06-23 22:00 ` John R. Culleton
2006-06-23 22:48 ` John R. Culleton
2006-06-24 7:46 ` Peter Münster
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=200606231017.17609.john@wexfordpress.com \
--to=john@wexfordpress.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).