[haiku-development] Re: To __BEOS__ or not to __BEOS__?

Andreas Färber <andreas.faerber@xxxxxx> wrote:
> > I thought we wanted to be source and binary compatible with BeOS
> > for
> > R1...
> > doing so before R1 would break source level compatibility, so I
> > would
> > avoid doing that.
> We've already broken source compatibility by removing the libnetwork
> symlinks then. Might it be an option to make this configurable in
> Jam?
> That is, if some variable or parameter is specified, create a strict
> development package (without libsocket, __BEOS__ etc.), and by
> default
> keep it source-compatible?

I don't really see a point in staying 100% source compatible - the
changes Haiku requires are minimal at most.


Other related posts: