On 09/22/2013 05:41 PM, Ryan Leavengood wrote:
On Sat, Sep 21, 2013 at 8:05 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: It sounds like your reasoning is sound with regards to the weird dependency between /boot/system and /boot/common, and I definitely agree that everything which the system requires to run should be in the system. But if /boot/common is to be removed, how will system-wide software be installed?
I might have been a bit unclear about that: /boot/system would take over all responsibilities of /boot/common, i.e. all software that shall be installed system-wide would be put there, and it would get the writable directories settings, var, and cache. pkgman's default installation location, which is currently common, would become system. From an end-user perspective things would just get simpler, because one would only have two installation locations (system and home) instead of three and it would be clearer what their purpose is (system-wide vs. per-user software installation).
I would also wonder how one would go about overriding some software provided by the system. Such as an example close to my heart: overriding the system provided Freetype, which lacks code for proper subpixel text rendering, with one which does have that code.
If that replacement software is packaged and lives in a repository, that repository can be added to the ones you want to install software from (e.g. via "pkgman add-repo ...") with a higher priority than the HaikuPorts repository, and an update of that software requested (not tested yet). If it is packaged but not in a repository you could just manually replace the package. If it is not packaged, you could install the library in the non-packaged hierarchy of either installation location.
CU, Ingo
