FS#32312 - [ttf-dejavu] creates symlinks in install script

Attached to Project: Arch Linux
Opened by daaku (daaku) - Wednesday, 31 October 2012, 05:59 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 01 November 2016, 23:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

Package ttf-dejavu creates symlinks in it's install script rather than installing the files as part of the package.

/etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf
/etc/fonts/conf.d/20-unhint-small-dejavu-sans.conf
/etc/fonts/conf.d/20-unhint-small-dejavu-serif.conf
/etc/fonts/conf.d/57-dejavu-sans-mono.conf
/etc/fonts/conf.d/57-dejavu-sans.conf
/etc/fonts/conf.d/57-dejavu-serif.conf

Additional info:
* package version(s): 2.33-3
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 01 November 2016, 23:09 GMT
Reason for closing:  Implemented
Comment by Greg (dolby) - Wednesday, 31 October 2012, 09:28 GMT
All files in /etc/fonts/conf.d/ are symlinks to /etc/fonts/conf.avail/
Comment by Antonio Rojas (arojas) - Wednesday, 31 October 2012, 11:30 GMT
I think the point is not that those files are symlinks, but that they should be included in the package instead of being created in post-install (like it's done in the fontconfig package since 2.10)
Comment by Greg (dolby) - Thursday, 08 November 2012, 09:26 GMT
  • Field changed: Percent Complete (100% → 0%)
This is a valid request
Comment by Doug Newgard (Scimmia) - Tuesday, 12 May 2015, 16:31 GMT
ping? Any progress?
Comment by Piotr Jurkiewicz (piotrjurkiewicz) - Tuesday, 12 April 2016, 01:10 GMT
Patch attached.

Note that upgrade would require --force option, or manual removal of these symlinks before it (similarly as here: https://www.archlinux.org/news/fontconfig-2101-update-manual-intervention-required/).

Alternatively, it could be handled automatically, but this would require a change in libalpm/pacman: run `pre_install` and `pre_upgrade` scripts BEFORE files conflicts check, not after it. Such a change would allow to automatically solve similar problems* in the future, without the need of manual intervention.

* https://bbs.archlinux.org/viewtopic.php?id=196909

Loading...