Bug#963708: fonts-fantasque-sans: rename directory to /usr/share/fonts-fantasque-sans
Package: fonts-fantasque-sans
Version: 1.7.2~alpha.3~dfsg-2
Severity: wishlist
Dear Maintainer,
fonts-fantasque-sans package provides files in
`/usr/share/fantasque-sans/` directory, while it seems there's a common
pattern to store fonts in `/usr/share/fonts-foo-bar` directory (or
/usr/share/foo/fonts/bar`, or just `/usr/share/fonts/foo`).
This will make easier for (at least) AppArmor profile writers, willing
to allow reading all font files.For example, we have to use some sort of
out-of-place exception for fantasque files like this:
```
/usr/share/fonts/** r,
/usr/share/fonts-*/** r,
/usr/share/*/fonts/** r,
/usr/share/fantasque-sans/** r, # why? :(
```
Anyhow, making path more semantic would be good for consistency, even if
ignoring lazy AppArmor contributors :) .
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
Reply to: