From: ishamid <ishamid@lamar.colostate.edu>
Subject: Upgrading...
Date: Sat, 5 Mar 2005 10:33:30 -0700 [thread overview]
Message-ID: <42305C77@webmail.colostate.edu> (raw)
Dear syndicate,
While I have not closely kept up with all developments it seems that
installation/upgrade procedures have been improved. I also went through a lot
of pain the last time I upgraded so I ask:
Given that:
1. I have not updated my context since Aug. of last year;
2. my fpTeX is from last July.
What is the wisest and most efficient way to upgrade my ConTeXt distribution
today?
Should I replace fpTeX (including Aleph) with the ConTeXt/TeX distribution
from the website?
Are there any Aleph-related issues?
Any tips will be appreciated
Thanks
Idris
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-03-05 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 17:33 ishamid [this message]
2005-03-05 22:51 ` Upgrading h h extern
2005-03-15 18:38 ` Upgrading Idris Samawi Hamid
2005-03-16 21:14 ` Upgrading Hans Hagen
2005-03-17 10:48 ` Upgrading Patrick Gundlach
2005-03-15 23:08 Upgrading ishamid
2005-03-16 9:02 ` Upgrading Hans Hagen
2005-03-15 23:09 Upgrading ishamid
2005-03-16 1:10 Upgrading ishamid
2005-03-16 8:57 ` Upgrading Hans Hagen
2005-03-16 14:32 Upgrading ishamid
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=42305C77@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).