#10045: PM: Putting fonts in non-packaged/data/fonts does not seem to work -------------------------+---------------------------- Reporter: stippi | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -------------------------+---------------------------- Comment (by stippi): I thought the idea is that /boot/common is merged from both the packages and the contents of non-packaged. B_COMMON_FONTS_DIRECTORY should still point to /boot/common/data/fonts. Why is there the need to have additional directories? Obviously that would not only break our own applications. WonderBrush for example looks in B_COMMON_FONTS_DIRECTORY and is still broken even when app_server is fixed. It has its own font engine. Doesn't that mean it is not transparent any more to applications, which stuff stems from packages and which from non-packages? How does it work for libraries? I thought a library could shadow a packaged library by putting a version in home/config/non-packaged/lib, which then appears in home/config/lib, shadowing any version from packages in home/config/packages. I would find it intuitive if it worked the same for fonts, or rather all of the folders in that hierarchy. -- Ticket URL: <http://dev.haiku-os.org/ticket/10045#comment:3> Haiku <http://dev.haiku-os.org> Haiku - the operating system.