HAIKU package management has broken the haiku file structure.
|Reported by:||bbjimmy||Owned by:||nobody|
|Has a Patch:||no||Platform:||x86|
60 to 80 percent of the third party software for Haiku has been broken by changes to the file system. The user guide describes the proper use of the /boot/common and /boot/home/config directory trees. These are now broken. Software that expects to add a binary or lib in either tree cannot. Scripting that expects binarys in /boot/home/config/bin or /boot/common/bin cannot find the binary in the /boot/home/config/non-packaged/bin directory.
The package management scheme has not kept to the design criteria:
Package management should be a convenient add-on to Haiku.
Package management must not change how a user deals with his system.
Package management must not break other software.
It would be nice to think that all software used on haiku will eventually be packaged in an .hpkg file. This is not now and will never be the case. Haiku needs the application developers. Breaking all their hard work is not a way to keep them interested in developing software for haiku.
To fix this:
/boot/home/config/bin and /boot/home/config/lib must not be read only.
return /boot/common and make it read/write.
Place packaged libs and binarys in /boot/home/config/packaged/bin and /boot/home/config/packaged/lib and these can be read-only.
When running a packaged file. ignore /boot/home/config/bin, /boot/home/config/lib, /boot/common/bin, and /boot/common/lib as these are not accounted for with the package management.
This will un-break all of the software that has been broken with package management and give the developers back the platform they developed their programs to run on. It will then make the .hpkg file a plus for the devs, not an un-do burden.