On 2012-09-06 Cyril Brulebois <k...@debian.org> wrote:
[...]
> Let's assume you were talking about fontconfig's README.Debian instead;
> it has:
> | If you wish to enable bitmapped fonts manually, either reconfigure this
> | package (with dpkg-reconfigure fontconfig-config), or remove the
> | symbolic link /etc/fonts/conf.d/30-debconf-no-bitmaps.conf
> (A) The filename is wrong.
> (B) Removing the symlink is documented and not honored.
Hello,
I have stumbled upon this bug while browsing the rc-bug list. This
looks like a documentation issue to me.
Imho fontconfig-config does not abuse debconf as a registry. It basically
follows debconf-devel(7) to manage (inter alia)
/etc/fonts/conf.d/70-{no,yes}-bitmaps.conf. (With the significant
value being the filename, not where the link points to.):
fontconfig-config.config checks whether
/etc/fonts/conf.d/70-no-bitmaps.conf or
/etc/fonts/conf.d/70-yes-bitmaps.conf exist and sets the debconf value
accordingly. (Otherwise the value currently present in debconf-db is
used.) Then the debconf question is asked. postinst afterwards sets up
the link according to the debconf-db.
Which I would not consider buggy. If one does the correct thing (rm -f
/etc/fonts/conf.d/70-*-bitmaps.conf && ln -s
/etc/fonts/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d/) the
change stays and propagates to debconf. It is just not yet documented.
/usr/share/doc/fontconfig/README.Debian seems to be outdated.
* /etc/fonts/conf.d/30-debconf-no-bitmaps.conf was the filename used in
old versions of fontconfig (< 2.4.x?)
* The package one needs to reconfigure is not fontconfig but
fontconfig-config.
* Link deletion is not supported.
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
