From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Portable linux Minimals installation?
Date: Mon, 29 Nov 2010 15:43:31 +0100 [thread overview]
Message-ID: <AANLkTika-4oix3mAMf+V7ZPhurAinZ+xhuF-wNseNR1E@mail.gmail.com> (raw)
In-Reply-To: <87eia4gpnx.fsf@universe.krase.net>
On Mon, Nov 29, 2010 at 15:39, Marco Pessotto wrote:
>
> It's happening to me that I have to travel to a place where there's no
> broadband access, and I'd like to take ConTeXt with me. So I can't just
> run the installer and rsync the trees. Now, the question is: is it safe
> to tarball the ConTeXt root directory with executable and texmf trees,
> and move it around (on another machine)? Or are there hardcoded paths
> that prevents this?
No, there are no hardcoded paths. You may even fetch both linux and
linux-64 architectures in parallel (or all the architectures), so that
it will work on any architecture. The only "somehow hardcoded" path is
the name of folder inside luatex-cache, but that's easy to
change/recover (you may simply delete contents of luatex-cache and
rerun mtxrun --generate).
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-29 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 14:39 Marco Pessotto
2010-11-29 14:43 ` Mojca Miklavec [this message]
2010-11-29 14:56 ` Marco Pessotto
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=AANLkTika-4oix3mAMf+V7ZPhurAinZ+xhuF-wNseNR1E@mail.gmail.com \
--to=mojca.miklavec.lists@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).