If this is really only about the search paths for libraries and add-ons we could as well add a simple feature to our runtime loader: From the executable file it could read attributes like BEOS:LIBRARY_PATH and BEOS:ADDON_PATH, which would override or extend the search paths. E.g. "%A:%A/components:%P" for prepending the application dir and its "components" subdir to the path.CU, Ingo
Nice idea, IMO:)