Re: Configuration file shadowed?

2006-07-24 Thread Frank Küster
Manoj Srivastava [EMAIL PROTECTED] wrote: The later is not so clear to me -- the distinction is blurred a bit, but I tend to agree than not. How does one feel about a LaTeX package that sets up a default output style, and the user prefers a different one? If there is a way to

Re: Bug#379089: Configuration file shadowed?

2006-07-23 Thread Norbert Preining
Hi all! Short comment from TeX live side, out of St. Moritz before leaving to mountains: On Fre, 21 Jul 2006, Frank Küster wrote: - files that can be used to modify the behavior of programs, and/or files that make sense to customize site-wide behavior on a multiuser system (I just

Re: Configuration file shadowed?

2006-07-23 Thread Manoj Srivastava
On Sat, 22 Jul 2006 18:12:46 +0200, Frank Küster [EMAIL PROTECTED] said: I've come across at least one example where it is: \ProvidesFile{listings.cfg}[2004/09/05 1.3 listings configuration] \def\lstlanguagefiles {lstlang0.sty,lstlang1.sty,lstlang2.sty,lstlang3.sty} If you have

Re: Configuration file shadowed?

2006-07-22 Thread Frank Küster
Manoj Srivastava [EMAIL PROTECTED] wrote: On Fri, 21 Jul 2006 21:54:50 +0200, Frank Küster [EMAIL PROTECTED] said: Indeed, the TeX Policy needs rewording, and this particular file should be a conffile, because it affects how the TeX programs and helper scripts act. In general, files that

Re: Bug#379089: Configuration file shadowed?

2006-07-22 Thread Ralf Stubner
On Sat, Jul 22, 2006 at 18:12 +0200, Frank Küster wrote: foo.tex (or foo.sty in most cases) is indeed a library equivalent, but we are rather discussing whether an additional foo.cfg or foo.whatever that is loaded by foo.sty is a configuration file or not. I've come across at least one

Re: Configuration file shadowed?

2006-07-21 Thread Frank Küster
Manoj Srivastava [EMAIL PROTECTED] wrote: What does this imply? Why are configuration files (I am assuming that something called mktex.cnf is actually a configuration file) being installed in /usr/share/? I didn't notice that this was Cc'ed to -devel, and already answered to Manoj,

Re: Configuration file shadowed?

2006-07-21 Thread Manoj Srivastava
severity 379089 serious thanks Hi, On Fri, 21 Jul 2006 09:57:20 +0200, Frank Küster [EMAIL PROTECTED] said: Because of this paragraph from the TeX Policy Draft: , 4.1 Configuration files | In a TeX system, in principle every TeX input file can be changed to | change the behavior of the

Re: Configuration file shadowed?

2006-07-21 Thread Jean-Christophe Dubacq
Le 21 juil. 06 à 18:23, Manoj Srivastava a écrit : While it is true any file can be changed to change behaviour for TeX (like things can be changed in /usr/include/foo.h to change behaviour of a -dev package), any file with a name *.cnf is meant to be a configuration file, and must,

Re: Bug#379089: Configuration file shadowed?

2006-07-21 Thread Frank Küster
Manoj Srivastava [EMAIL PROTECTED] wrote: severity 379089 serious thanks While it is true any file can be changed to change behaviour for TeX (like things can be changed in /usr/include/foo.h to change behaviour of a -dev package), any file with a name *.cnf is meant to be a

Re: Bug#379089: Configuration file shadowed?

2006-07-21 Thread Christoph Berg
Re: Frank Küster 2006-07-21 [EMAIL PROTECTED] I believe that we need to rephrase the TeX Policy. But this requires not just to specifiy that each cfg file must be in /etc. Instead, I think we need to find a distinction between - files that can be used to modify the behavior of programs,

Re: Configuration file shadowed?

2006-07-21 Thread Steve Greenland
On 21-Jul-06, 13:41 (CDT), Jean-Christophe Dubacq [EMAIL PROTECTED] wrote: The way I see it, the /usr/share/texmf/mktex.cnf is a default value file, used in the setup of the whole texmf hierarchy; the configuration is /etc/texmf/mktex.cnf, which, per web2c magic, overrides the default

Re: Configuration file shadowed?

2006-07-21 Thread Manoj Srivastava
On Fri, 21 Jul 2006 20:41:38 +0200, Jean-Christophe Dubacq [EMAIL PROTECTED] said: Le 21 juil. 06 à 18:23, Manoj Srivastava a écrit : While it is true any file can be changed to change behaviour for TeX (like things can be changed in /usr/include/foo.h to change behaviour of a -dev

Re: Configuration file shadowed?

2006-07-21 Thread Frank Küster
Steve Greenland [EMAIL PROTECTED] wrote: On 21-Jul-06, 13:41 (CDT), Jean-Christophe Dubacq [EMAIL PROTECTED] wrote: The way I see it, the /usr/share/texmf/mktex.cnf is a default value file, used in the setup of the whole texmf hierarchy; the configuration is /etc/texmf/mktex.cnf, which,

Re: Bug#379089: Configuration file shadowed?

2006-07-21 Thread Frank Küster
Christoph Berg [EMAIL PROTECTED] wrote: Re: Frank Küster 2006-07-21 [EMAIL PROTECTED] I believe that we need to rephrase the TeX Policy. But this requires not just to specifiy that each cfg file must be in /etc. Instead, I think we need to find a distinction between - files that can be

Re: Configuration file shadowed?

2006-07-21 Thread Frank Küster
Manoj Srivastava [EMAIL PROTECTED] wrote: The difference here is that if you follow this path, ad eschew the conffile mechanism, it is up to you to provide the benefit to users that conffile mechanisms provide: namely, the user is informde when the maintainer changes default

Re: Configuration file shadowed?

2006-07-21 Thread Manoj Srivastava
On Fri, 21 Jul 2006 21:54:50 +0200, Frank Küster [EMAIL PROTECTED] said: Steve Greenland [EMAIL PROTECTED] wrote: On 21-Jul-06, 13:41 (CDT), Jean-Christophe Dubacq [EMAIL PROTECTED] wrote: The way I see it, the /usr/share/texmf/mktex.cnf is a default value file, used in the setup of the

Configuration file shadowed?

2006-07-20 Thread Manoj Srivastava
Hi, Today, when upgrading my unstable box, I got a debconf message from the package tex-common, to wit: “The mechanism of TeX font caching has changed, requiring the installation of /usr/share/texmf/web2c/mktex.cnf. On your system, /etc/texmf/web2c/mktex.cnf