Bug#607857: tex-common: Hard-coded path in proposed patch
On Mon, Jan 03, 2011 at 09:41:04AM +0100, Hilmar Preusse wrote:
> Happy new year,
>
> > > Not good[TM]. I'll open a wishlist bug to have that changed. Should
> > > be that hard to source /etc/texmf/texmf.cnf at the beginning of these
> >
> > Can you transplant the X hierarchy somewhere else? I suspect not.
> > Can you move /usr/share/gnome-* somewhere else? I suspect not.
> >
> I didn't check, but I suspect these packages don't even pretend this
> would be possible. We have a config file where things can be changed
> and it may happen that people expect this can be done.
>
> And yes: I don't see either a good reason to do so.
Happy new year to all, too!
Most significantly, the tex-common postinst is designed to handle the
installation of new files through the package maintenance system. The
files in those packages will be installed into the standard places on
the system, and tex-common behaves accordingly:
/usr/share/texmf{,-texlive} and /var/lib/texmf are the directories
handled by packages, and therefore tex-common should use those same
directories.
If a sysadmin wished to change this, they would have to divert every
single package installation - I can imagine this being painful and
pointless....
Ho hum ....
Incidentally, the advice about using --nohash should be included in
the Debian TeX Policy so that other packages don't stumble upon this
bug.
Julian
Reply to: