ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Context install from Texlive2016 mtxrun problem
Date: Tue, 28 Feb 2017 17:34:20 +0100	[thread overview]
Message-ID: <5597bda6-8f8f-6cd0-4c81-7414eb52c190@gmx.es> (raw)
In-Reply-To: <4b17213c-d013-9095-e971-10ac684cd9cf@gmail.com>

On 02/28/2017 02:23 PM, Geert Dobbels wrote:
> Hello,
> 
> After several years away from Context, I would like to start using it 
> again and encounter the following problem:
> 
> I am on a Fedora 25 system, 64bit machine and installed context from the 
> rpm repositories via dnf.  The repositories contain a Texlive 2016 version.
> 
> I installed "texlive" and "texlive-context" from those repositories, and 
> context works out of the box.

Hi Geert,

I’m on Fedora 25, but my laptop is old (so, mine is a 32bit machine).

When I came back to ConTeXt, I installed it from TeX Live. But after
some use (and the kind advice from different people in this list), I
decided to install the ConTeXt Suite.

It is as simple as:

time (cd && mkdir temp-ctx-install && cd temp-ctx-install &&\
rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . &&\
./first-setup.sh --modules=all && cd &&\
source temp-ctx-install/tex/setuptex && mtxrunjit --generate)

With a decent internet connection it only takes two minutes to download
(the command "time" is there to measure things ;-)).

Why do I write this? Because I had the same thoughts (“Installing a beta
version? Crazy!”). And now I don’t have any other TeX distribution
installed on my system ;-).

Since the installation is portable, you may install it besides your TeX
Live ConTeXt. Depending on your free space available, you may have
different betas in the same computer. After all, they aren’t installed
on the system.

All you have to do is to invoke (before running ConTeXt):

  source /directory-where-context-suite-is-placed/tex/setuptex

All paths will be loaded and everything will be fine.

Using the current beta, you have latest implementations available and
you avoid dealing with ancient bugs.

BTW, "mtxrun --generate" might help you with the issue you reported.
(Not tested, since I don’t want to install TeX Live :-).)

Just in case it helps,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-02-28 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 13:23 Geert Dobbels
2017-02-28 16:34 ` Pablo Rodriguez [this message]
2017-02-28 22:10   ` Geert Dobbels

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=5597bda6-8f8f-6cd0-4c81-7414eb52c190@gmx.es \
    --to=oinos@gmx.es \
    --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).