Re: Bug#189370: acknowledged by developer (irrelevant)
From: Manoj Srivastava <srivasta@debian.org>
Subject: Re: Bug#189370: acknowledged by developer (irrelevant)
Date: Mon, 21 Apr 2003 20:45:44 -0500
> For example, I set up a Debian machine in a lab with other,
> non debian machines. I note that all the machines have default
> texmf.cnf behaviour. No problem, I create a custom texmf.cnf, and
> distribute it to all machines.
I don't know how you create texmf.cnf but it would be enough
if you create it in Debian and distribute it to other machines
(but under the condition that you use only compatible TeX
components which is your case, perhaps).
But it seems you dislike it by some reason or other and they
are your machines so it's okay how you treat them and to complain
or to file a bug as you like.
> Every other machine works. But the Debian box, despite having
> my nice, fancy, /etc/texmf.cnf, does not pay any attention to it.
Ditto.
> Hmm. Red Hat Works. Suse Works. Solaris Works. Debian fails.
> Why does Debian have to be incompatible? I say this is a bug.
Ditto.
Because RedHat, for example, is a comercial distribution so
RedHat would be designed from the biginning what TeX components
it would include, therefore a static texmf.cnf worked. Further,
RedHat doesn't have something similar to our policy, perhaps,
so it can modify texmf.cnf freely if necessary, I guess.
(Correct me if I misunderstand RedHat. I've never used it.)
On the other hands, in Debian which is an association of
volunteers, a developer can package any DFSG-free TeX components
or DFSG-free extra fonts packages freely so we need an infra-structure
which provides dynamic texmf.cnf etc. so that every such extra
packages can modify texmf.cnf in order that they could be installed and
work without problem. I believe this is our (tetex-mantainers') duty.
From: Manoj Srivastava <srivasta@debian.org>
Subject: Re: Bug#189370: acknowledged by developer (irrelevant)
Date: Mon, 21 Apr 2003 20:48:14 -0500
> In he old
> scheme, my changes were never lost.
If you like the old scheme, it is possible only if policy
doesn't forbid to modify a conffile, texmf.cnf, by packages'
scripts. (In fact, some packages did it before.)
BTW, does policy force us that our configurations should be
compatible with those of RedHat?
Thanks, 2003-4-23(Wed)
--
Debian Developer & Debian JP Developer - much more I18N of Debian
Atsuhito Kohda <kohda@debian.org>
Department of Math., Tokushima Univ.
Reply to: