ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Olivier <billet@eurecom.fr>
Subject: Re: Debian Install
Date: Sat, 15 Oct 2005 15:50:23 +0200	[thread overview]
Message-ID: <20051015135023.GA11655@blackowl.org> (raw)
In-Reply-To: <4350EDF4.4050807@wxs.nl>

Quoting  "Hans Hagen" :
> -- was pragma@wxs.nl on Oct 15, 2005 at 01:54:28 --

> Olivier wrote:
> 
> >Actually, the file texmf.cnf should be located at /etc/texmf/ like all
> >the config files for the tetex distrib (and I assume the 
> >/usr/share/texmf/web2c
> >is just a link from there).

> actually, moving all such files to etc is a bad idea; if etc really wants 
> that file there (maybe under /etc/web2c), best make a symlink from there to 
> the formal place tex tree; makes updating easier; a lot of effort goes into 
> making the tex tree clean and self contained, so moving files outside the 
> tree is a bad idea. 

I understand some people may have different views. I was just trying to
tell the way it is done in the Debian GNU/Linux system.
There is a policy about TeX stuff location inside the system which is
described in the Debian TeX policy here:
        http://people.debian.org/~frank/Debian-TeX-Policy
This includes as you can read in the first paragraph on config:
        The central configuration file for TeX applications is
        /etc/texmf/texmf.cnf, the central font configuration file is
        /var/lib/texmf/web2c/updmap.cfg, the central
        language/hyphenation configuration
        /var/lib/texmf/tex/generic/config/language.dat, and format
        generation is determinded by /var/lib/texmf/web2c/fmtutil.cnf.
        All four files are generated by configuration update programs
        from configuration files in subdirectories of /etc/texmf.

That's how it is, and was'nt involved in the making of this policy :)
The original poster was asking for the normal setting in his Debian
system and I believe it is correct. Moreover, it is always a bad idea to
move files provided by packages: I know you are providing a sync
mechanism for conTeXt but you'll certainly understand that doing this
for every set of program in a system is something a sysadmin does'nt
want to go into, and I guess that's where packaging system originated ;)

Cheers,
Olivier

  reply	other threads:[~2005-10-15 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 20:35 K. David Prince
2005-10-15  8:34 ` Olivier
2005-10-15 11:54   ` Hans Hagen
2005-10-15 13:50     ` Olivier [this message]
2005-10-17  8:25       ` Hans Hagen
2005-10-15 17:27 Idris Samawi Hamid
2005-11-17  8:09 Jessica Holle
2005-11-17  8:43 ` 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=20051015135023.GA11655@blackowl.org \
    --to=billet@eurecom.fr \
    --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).