Bug#38290: tetex-base: postscript fonts, psfonts.map and tetex updates
On 26.05.99 Ulf Jaenicke-Roessler (ujr@physik.phy.tu-dresden.de) wrote:
> Christoph Martin wrote:
Hi all,
> > /etc/texmf/dvips/psfonts.map is a confile which you can change and
> > which will not be overwritten on update if you don't request it. What
> > is your problem with this?
>
> Well, may be my reasons aren't satisfactory for you. Anyway, here
> they are.
>
> After one of the last teTeX updates the psfonts.map file was
> updated in the deb and I indeed chose to keep my changed version.
> However I thought there must be a reason that the package
> maintainer changed the file (there was one, right? ;-), so I tried
> diff. I nearly always do that with conffiles, when I made changes
> to it. Mostly there are only a few changes by the package
> maintainer.
> Unfortunately there seemed to be a lot of changes here, although
> some of them were only caused by moved lines. But it was difficult
> to recognize what really changed. One reason is, that the file is
> not easy to read (at least for TeX beginners, I guess).
>
> So I thought that there could be a simpler way to get a "personal"
> psfonts.map file. Maybe one, which is created on install time during
> postinst.
>
Yes, there is. Until the advent of teTeX 2.0 the normal way was to
edit /etc/texmf/updmap, add your map file, put it into
/etc/texmf/dvips and then call that script.
Since teTeX 2.0 you have to edit updmap.cfg, add your map file to it,
put it into /etc/texmf/dvips and then call updmap. The normal Debian
way to do it is to put the part of updmap.cfg, which mentions your
map-file into /etc/texmf/updmap.d/, the map-file into
/etc/texmf/dvips, call update-updmap and updmap and you're done.
In this case updmap.cfg is generated. This can be unselected using
debconf. If you did that updmap.cfg is sitting in /etc and you have
to edit it manually.
The font configurations files pdftex, pd2pk, psfonts should never be
touched. So I don't understand your bug report completely.
> BTW, another reason which could justify such an addition, would be
> the possibility to create (at least local) deb packages for PS
> fonts and "register" them automatically.
>
This is possible.
H.
--
sigmentation fault
Reply to: