On 10/26/2011 01:42 PM, Christian PERRIER wrote: > The more we go, the more this package renamingn business becomes > complicated (OK, I complicated it by moving the files, but I wasn't > actually expecting that some packages would hardcode the font paths). More generally, do we have a set of recommended best practices for tools which might need to search for fonts? If we had a clearly-stated recommendation that would be an improvement over hard-coded paths, we could just file bugs against packages that use hard-coded paths and let them suffer the consequences of possible renames/moves. To be clear, I'm not just interested in making this "not our problem" -- having such a recommendation would improve the robustness of the packages in the archive. --dkg
Attachment:
signature.asc
Description: OpenPGP digital signature