From: Mari Voipio <mari.voipio@iki.fi>
Subject: Re: 2c considerations about win installer
Date: Sat, 22 Apr 2006 16:33:49 +0300 [thread overview]
Message-ID: <444A30BD.4010400@iki.fi> (raw)
In-Reply-To: <pan.2006.04.22.10.26.40.669678@gmail.com>
olivier wrote:
> Your students can also install Ruby (single click .exe
> : Rubyinstaller from
> : http://rubyforge.org/frs/download.php/9417/ruby184-16_rc1.exe)
> and Perl (single click .exe : activePerl
> :http://www.activestate.com/Products/ActivePerl/) whithout any pb's of
> adding new executables to the path, since it's done while installation.
Except that I found out the very hard way, that at least Ruby installs
nicely for a power user, but doesn't change the path unless the
installation is done when logged in as Administrator - which may be a
problem in a multi-user environment.
Other than that, I haven't had any problems with newer versions of the
MSWinConTeXt distribution (the one that unzips into 'isoimage' folder).
I'm currently running the April 10 version from CD at work and once Perl
and Ruby got installed into the path, the system has been really easy to
use. [I downloaded the mswincontext.zip, unzipped and burned the
*contents* of the isoimage folder onto a CD - and that's it, then.)
Yes I agree, it is harder to put a working ConTeXt into Windows than
into a Mac where it was *very* easy, but with Administrator rights to
Windows2000/XP, the abovementioned Perl and Ruby installation packages
are no problem and after that things just work.
Mari
(multi-OS user, but best in Windows)
prev parent reply other threads:[~2006-04-22 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 23:33 andrea valle
2006-04-21 7:43 ` Jilani Khaldi
2006-04-21 11:41 ` Hans Hagen
2006-04-22 16:20 ` Mojca Miklavec
2006-04-23 14:25 ` andrea valle
2006-04-23 16:12 ` Hans Hagen
2006-04-23 17:40 ` andrea valle
2006-04-23 16:30 ` Hans Hagen
2006-04-22 10:26 ` olivier
2006-04-22 13:33 ` Mari Voipio [this message]
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=444A30BD.4010400@iki.fi \
--to=mari.voipio@iki.fi \
--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).