From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Geeze, I might try Linux after all... (not too off-tpic I hope)
Date: Fri, 20 Jun 2008 10:17:28 +0200 [thread overview]
Message-ID: <326847810806200117y3a98e1ddlb6594b5c088ce83d@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00806200003s57f528aahf6729ee562297a11@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 796 bytes --]
I don't understand. Please explain...
(1) >You cannot update the binaries that way (you are not supposed to :).
Why can't the binaries be updated that way (why aren't we supposed to) ?
(2) >On your own risk, you may update the binaries from minimals
> rsync -av \
> rsync://contextgarden.net/minimals/current/bin/xetex/linux/bin/ \
> /path/to/bin/with/xetex
Why on your own risk ?
Thanks a lot for clearing up the mist,
Alan
On Fri, Jun 20, 2008 at 9:03 AM, Mojca Miklavec <
mojca.miklavec.lists@gmail.com> wrote:
> You cannot update the binaries that way (you are not supposed to :).
>
> On your own risk, you may update the binaries from minimals
> rsync -av \
> rsync://contextgarden.net/minimals/current/bin/xetex/linux/bin/ \
> /path/to/bin/with/xetex
>
> Mojca
>
>
[-- Attachment #1.2: Type: text/html, Size: 1452 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-20 8:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 10:28 Alan Stone
[not found] ` <326847810806130328k73f9ed0bw4ec3ede296a29d55@mail.gmail.co m>
2008-06-13 10:42 ` Alan Stone
2008-06-13 12:09 ` luigi scarso
2008-06-13 12:38 ` Michael Hallgren
2008-06-13 13:07 ` Diego Depaoli
2008-06-13 12:53 ` Olivier Guéry
2008-06-13 13:37 ` Charles P. Schaum
2008-06-13 14:53 ` John Devereux
2008-06-14 6:20 ` Alan Stone
2008-06-14 7:29 ` Alan Stone
2008-06-14 7:40 ` Taco Hoekwater
2008-06-14 9:07 ` luigi scarso
2008-06-14 9:38 ` Matija Šuklje
2008-06-14 11:25 ` John Culleton
2008-06-19 19:40 ` Alan Stone
2008-06-20 6:37 ` Wolfgang Schuster
2008-06-20 6:45 ` Alan Stone
2008-06-20 7:03 ` Mojca Miklavec
2008-06-20 8:17 ` Alan Stone [this message]
2008-06-20 12:21 ` Alan Stone
2008-06-20 12:27 ` Wolfgang Schuster
2008-06-20 13:39 ` Alan Stone
2008-06-20 14:31 ` Mojca Miklavec
2008-06-20 16:21 ` Alan Stone
2008-06-20 21:05 ` Aditya Mahajan
2008-06-21 7:44 ` Alan Stone
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=326847810806200117y3a98e1ddlb6594b5c088ce83d@mail.gmail.com \
--to=software.list.1es9s@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).