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

Bug#141086: tetex-bin: Puts files in /usr/local



"DC" == Dan Christensen <jdc@uwo.ca>


    DC> I think there are still a few minor problems.  First, the
    DC> postinst contains

    DC> if [ -e $TEXCONFIG_P -a -e /usr/share/texmf/dvips/config ]
    DC> then ...  /usr/bin/mktexlsr ...

    DC> which writes a file to /usr/local.  Maybe the new logic
    DC> should be moved from the cron.daily script to mktexlsr?
    DC> Or a wrapper should be put around mktexlsr?

I agree that modifying mktexlsr would be the best thing to do, and
that was my first attempt at solving the problem.  Unfortunately,
mktexlsr is a fairly nightmarish Bourne shell script, and my
Bourne shell scripting is (*ahem*) not the greatest.  (Give me
Perl any day.)

It's fairly trivial to modify the postinst script in a similar way
to the way I modified the cron.daily script, though.

    DC> And the FHS=1 or 0 setting could be put into either of
    DC> these places, or into a file in /etc/texmf/.  The latter
    DC> is better, because then it could be used in the following
    DC> ways:

    DC> 1) Maybe texmf.cnf could be made to look at the FHS
    DC>    setting too, and use !! if FHS=0.  Then the user has to
    DC>    only change one spot if they want to have local ls-R
    DC>    files.  If it is hard to have conditionals in
    DC>    texmf.cnf, then instead comments could be put both in
    DC>    texmf.cnf and where FHS is set.

    DC> 2) On upgrade, if FHS=1, then I think the package should
    DC>    remove any existing ls-R file.  Otherwise I think that
    DC>    people who haven't followed these changes will complain
    DC>    that their ls-R file is out of date.  Worse, if they
    DC>    see the ls-R file there but don't notice that it is out
    DC>    of date, they may update texmf.cnf to use it by adding
    DC>    !!.

Both of these are really good ideas.  I definitely think that the
FHS variable should be set in a configuration file.  Also, at the
moment, running texconfig runs mktexlsr, which happily tries to
write to /usr/local/{lib,share}/texmf/ls-R.

    DC> A simpler arrangement is to:

    DC> a) remove mktexlsr from postinst completely 

    DC> b) always remove all ls-R files on install/upgrade 

    DC> c) let the cron job handle making new ls-R files (and
    DC>    maybe run the cron job from the postinst)?

Hmm.  That sounds like a possibility.

    DC> Finally, maybe the FHS setting could be asked as a low
    DC> priority debconf question?

That would also probably be a good idea.

I'll think about it a bit, and maybe take another poke at the
mktexlsr script, as it makes sense to me to change the one script
with the issue, rather than several other things that call it.

   CMC

 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
 Man cannot be civilised, or be kept civilised by what he does in his
	    spare time; only by what he does as his work.
			     W.R. Lethaby
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
  C.M. Connelly               cmc@debian.org                   SHC, DS
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+


-- 
To UNSUBSCRIBE, email to debian-tetex-maint-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: