[haiku-development] Re: Removing /boot/common
- From: Jessica Hamilton <jessica.l.hamilton@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 17 Oct 2013 20:53:51 +1300
>
> I'd like to suggest the removal of the /boot/common hierarchy. We
> originally introduced it as a place where software could be installed
> globally, while /boot/system would contain a completely read-only,
> self-contained base system. Even if something broke in common, one would
> still be able to boot into the base system via a boot loader safe mode
> option. (I believe that was never implemented.)
>
> I don't expect a lot of problems due to removing /boot/common. BeOS never
> had it, so old software wouldn't mind. Anything newer should use
> find_directory(). There are a few packages that hard-code common paths --
> e.g. in search path lists (gcc, cmake) -- but that can be remedied and
> mostly doesn't have negative effects anyway. We have already aligned the
> internal layout of all installation locations, so that there shouldn't be
> any surprises in that department either.
>
> Thoughts, suggestions, flames,...?
>
With regard to removing B_COMMON_*, this is actually breaking the BeOS API.
Isn't one of the goals of Haiku R1 to also be source-compatible?
Although not a huge fan of multi-user possibly coming to Haiku, aren't you
also going to need these when that rolls around?
Jessica
Other related posts:
