#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): Replying to [comment:5 bonefish]: > Replying to [comment:3 stippi]: > > Doesn't that mean it is not transparent any more to applications, which stuff stems from packages and which from non-packages? > > Well, in the same way it isn't transparent which stuff stems from /boot/system and which from /boot/common or /boot/config/home. An enumeration of directories would not do. Ideally, there would be just one virtual directory, where all the shadowing and even turning off user add-ons and data (in safe-mode) is already taken care of. > > 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. > > No, the shadowing happens at the runtime loader level. The path ~/config /non-packaged/lib is simply listed before ~/config/lib in LIBRARY_PATH. Ok, but then it's not as elegant as I thought. I thought the directory structure stays the same on the surface, where package fs takes care of dynamically and magically blending the contents of packages and the non- packaged structure at these "old" directories. As it is, in various places, apps now need to be aware of package management, plus the non- packaged hierarchy as it turns out. -- Ticket URL: <http://dev.haiku-os.org/ticket/10045#comment:6> Haiku <http://dev.haiku-os.org> Haiku - the operating system.