From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: week of wiki 1: call for "installation instructions"
Date: Wed, 6 Feb 2008 21:37:00 +0100 [thread overview]
Message-ID: <52ADF48C-EBAC-4D5C-80B7-6AE80C2D88F7@fiee.net> (raw)
In-Reply-To: <6faad9f00802061203u21a2b4dfub35898d5560086b7@mail.gmail.com>
Am 2008-02-06 um 21:03 schrieb Mojca Miklavec:
>> I just cleaned up the Mac page (it was really messy)
> Now that I have seen a note about TeXShop, maybe a note about editors
> (TextMate) or link to page with editors and viewers (Skim) would be in
> place as well (at least a list of them).
Ok, I linked to Text_Editors - every further tool should be listed
there, not on the installation pages.
>> to the minimal distribution - that page goes under the bad name of
>> "Linux_User_Installation". I guess we should rename that.
> True, Linux_User_Installation should be more general since it works
> with any "unix".
> I have alse created a page
> http://wiki.contextgarden.net/ConTeXt_Minimals, but that one needs to
> be improved (too much junk on it - wiki pages need to be short and
> clear, else nobody reads them).
I can't help with that - I use TeXlive, updated with "ctxtools --
updatecontext".
> Hans has not updated his distribution since August (which means that
> there are still old binaries ond fonts) and we're working on improving
> the new minimals at the moment. The good side of it is that it uses
> rsync, and updates semi-automatically (binaries need to be rebuilt
> manually, and many parts need to be improved), the bad side of it is
> that if garden goes down, there is no backup server yet to fetch the
> binaries from (and if the disk stops working, I will need quite some
> time to get all the parts together again), and the structure might
> still change a bit.
Ok, we (you?) should explain the relationship between the minimals
hosted at "pragma-ade.com/context/install/" (Linux_User_Installation)
and that on "minimals.contextgarden.net" (ConTeXt Minimals).
I could provide some space on my webserver as backup (how much do you
need?), but I'd prefer to get no too much public traffic.
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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-02-06 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 14:50 Mojca Miklavec
2008-02-06 19:18 ` Henning Hraban Ramm
2008-02-06 19:46 ` Andrea Valle
2008-02-06 20:03 ` Mojca Miklavec
2008-02-06 20:37 ` Henning Hraban Ramm [this message]
2008-02-06 20:40 ` Taco Hoekwater
2008-02-06 20:42 ` Hans Hagen
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=52ADF48C-EBAC-4D5C-80B7-6AE80C2D88F7@fiee.net \
--to=hraban@fiee.net \
--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).