[haiku-development] Re: usr/bin

Marcus Overhagen wrote:

Rob Judd <haiqu@xxxxxxxxxx> wrote:


Axel Dörfler wrote:

Rob Judd wrote:

Until we go multi-user, could we have a symlink from /boot/system/bin to
/usr/bin please? It would make porting apps that call /usr/bin/env a
whole lot easier.

Even with multi user, there will never be a /usr directory in Haiku.
Porting is not just recompiling, and it deserves a bit more attention
(like to put the settings into the right place, or use the native Media
Kit instead of porting G-Streamer as well).
Not sure where you're planning to put user-accesible binaries then, and /usr/bin just seemed the obvious location.
We do have /boot/system/bin and /boot/common/bin. Using the common directory for anything that doesn't belong to the system seems to be obvious to me.
Right. Except that at the moment /boot/common/bin being used as a dumping ground for anything being built, and ./configure for everything points there. Not a wise choice. It's more an extension of /boot/system/bin that wasn't in the original BeOS.
I also am aware of the difference between merely compiling something and porting it, D'oh! But when a test suite uses Python and calls hundreds of scripts with #!/usr/bin/env python then the sensible thing to do is NOT edit the whole mess, but to install a simple symlink. I don't care what the _proper_ way to do that might be, the return isn't worth the effort when tests are run once and then immediately deleted once their results are known. 

Your test method is flawed. The users won't have a symlink, so their
result when running those scripts will be different from your result.
Rubbish! The end user will NEVER run the validation tests, and on the odd occasion when someone wants to do so my methods are documented at http://ports.haiku-files.org 


However, editing the test suite certainly isn't the sensible either.

I'm not sure if it's worth the effort to explain this, but certainly
a sensible way to provide compatibilty with those scripts would
be to implement a mapping inside the runtimeloader of the
standard unix #! directories to haiku directories.
Sounds like a complicated solution, considering that the average end-user will never look in the root directory. Complicated solutions don't impress me, I'm a pragmatist. For the last 35 years I've made a living making things work, fast. The subversion upgrade has been on the list for 21 months, so I built the damned thing. If you have a problem with that I suggest that might explain why this OS has taken 7 years to recreate. 

Rob

Other related posts: