From: Ed L Cashin <ecashin@uga.edu>
Subject: Re: texexec
Date: Thu, 12 Jun 2003 11:01:53 -0400 [thread overview]
Message-ID: <20030612110152.A9798@atlas.cs.uga.edu> (raw)
In-Reply-To: <200306121518.01026.Raimund.Kohl@freenet.de>; from Raimund.Kohl@freenet.de on Thu, Jun 12, 2003 at 03:18:01PM +0200
On Thu, Jun 12, 2003 at 03:18:01PM +0200, Raimund Kohl wrote:
> Hello there,
>
> I love working with ConTeXt, and never had to think about it much since SuSE
> makes it realy easy ... but now I switched to Debian, and all of a sudden
> have to face some trouble :-))
>
> I run Debian Woody 3.01r and if I call
I've been a debian woody user for a long time, now,
and the conclusion I eventually came to was this:
* debian's strict adherence to directory structure
conventions has made the tetex package difficult
to maintain, since it's split into many parts,
spread all over the filesystem. (This is really
just an inference of mine.)
* context has never worked for me in debian, and
submitting a bug report looks hopeless, given the
long length of the bug list. I haven't checked
in a long time, though.
* I wasn't able to use the "equivs" package to get
the debian packaging system to accept my own tetex
installation, so I could not install, e.g., the
docbook-xsl-st package.
* finally, I settled on this: install the debian
tetex packages but don't use them directly. Also
install teTeX from source in /opt, and set my
PATH so that when I say texexec I get the real
tetex and not debian's broken tetex.
Luckily, the price of disk space continues to drop. ;)
--
--Ed L Cashin | PGP public key:
ecashin@uga.edu | http://noserose.net/e/pgp/
next prev parent reply other threads:[~2003-06-12 15:01 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"from Raimund.Kohl"@freenet.de>
2003-06-12 13:18 ` texexec Raimund Kohl
2003-06-12 15:01 ` Ed L Cashin [this message]
2003-06-14 9:30 ` texexec Hans Hagen
2003-06-14 11:27 ` texexec Siep Kroonenberg
2003-06-13 15:57 ` texexec Raimund Kohl-Fuechsle
2003-06-13 16:00 ` texexec Raimund Kohl
2006-05-04 22:03 texexec Hans Hagen
2006-05-04 23:59 ` texexec Jilani Khaldi
2006-05-05 6:10 ` texexec luigi scarso
2006-05-05 13:26 ` texexec Steve Grathwohl
2006-05-05 13:36 ` texexec Renaud AUBIN
2006-05-05 15:16 ` texexec Hans Hagen
2006-05-05 14:09 ` texexec Steve Peter
2006-05-06 23:01 ` texexec Aditya Mahajan
2006-05-07 18:14 ` texexec Hans Hagen
2006-05-07 18:34 ` texexec Aditya Mahajan
2006-05-07 21:15 ` texexec Hans Hagen
2006-05-08 0:37 ` texexec Aditya Mahajan
2006-05-07 19:10 ` texexec Hans Hagen
2006-05-07 19:29 ` texexec Aditya Mahajan
2006-05-07 19:13 ` texexec Hans Hagen
2006-05-07 19:30 ` texexec Aditya Mahajan
2006-05-07 21:53 ` texexec Mojca Miklavec
2006-05-15 22:55 ` texexec frantisek holop
2006-05-15 23:06 ` texexec Hans Hagen
2006-06-19 21:46 ` texexec John R. Culleton
2006-06-19 21:13 ` texexec Hans Hagen
[not found] <Pine.LNX.4.44.0307012300450.9436-100000@twain.marshallward .net>
2003-07-02 18:08 ` Texexec Hans Hagen
2003-07-04 23:39 ` Texexec Marshall Ward
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 13:04 texexec Raimund Kohl-Fuechsle
2002-12-09 14:56 texexec Matthew Huggett
2002-12-09 19:25 ` texexec Henning Hraban Ramm
2001-02-10 19:02 texexec Giuseppe Bilotta
2001-02-11 8:23 ` texexec Marc van Dongen
2001-02-11 21:14 ` texexec Hans Hagen
2001-02-12 16:35 ` texexec Ed L Cashin
2001-02-12 18:48 ` texexec Taco Hoekwater
2000-02-08 6:16 TeXexec Dan Seracu
2000-02-08 8:33 ` TeXexec Gilbert van den Dobbelsteen
2000-02-08 9:33 ` TeXexec Dan Seracu
[not found] <375383E9.3A6BF93E@wxs.nl>
1999-06-01 19:34 ` texexec David Arnold
1999-06-02 7:26 ` texexec Hans Hagen
1999-04-22 12:31 texexec Thomas Esser
1999-04-23 7:09 ` texexec Hans Hagen
1999-04-22 12:13 texexec Thomas Esser
1999-04-22 14:28 ` texexec Taco Hoekwater
1999-04-22 9:05 texexec Erik Frambach
1999-04-22 11:31 ` texexec Erik Frambach
1999-04-22 12:12 ` texexec Taco Hoekwater
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=20030612110152.A9798@atlas.cs.uga.edu \
--to=ecashin@uga.edu \
--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).