[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#189370: acknowledged by developer (irrelevant)



On Tue, 22 Apr 2003 07:58:10 +0900 (JST), Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp> said: 

> From: Mark Brown <broonie@sirena.org.uk> Subject: Re: Bug#189370:
> acknowledged by developer (irrelevant) Date: Mon, 21 Apr 2003
> 11:23:26 +0100

>> On Mon, Apr 21, 2003 at 05:53:09PM +0900, Atsuhito Kohda wrote:
>> > From: Manoj Srivastava <srivasta@debian.org>
>>
>> > > 	So you do not understand the value of being compatible with
>> > >  other TeX installations? You think it is not arrogant for Debian to
>> > >  assume the rest of the world also runs Debian?
>>
>> > The current texmf.cnf of Debian is completely the same as the one
>> > upstream teTeX provided, if no local modification files are put
>> > in /etc/texmf/texmf.d/ There is no specific for Debian at all.
>>
>> As soon as the admin decides to make changes to it it becomes
>> incompatible with non-Debian installations.  If the admin changes
>> it using the Debian mechanisms then the other installations will
>> just ignore the changes.  If the admin changes it by just editing
>> the file then Debian will merrily come along and trash it.

> Yes but when the admin dicided to make (non-compatible) changes to
> texmf.cnf then it lost compatibility whether we used the old scheme
> or the new scheme.


	They are not non compatible. I have a central texmf.cnf that
 works all over my lab, with all the other operating systems. Only on
 Debian, my /etc/texmf/texmf.cnf is blown away periodically. In he old
 scheme, my changes were never lost. I just never told dpkg it was OK
 to replace my file. 

	manoj

-- 
Treat your friend as if he might become an enemy. Publilius Syrus
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



Reply to: