I would like to help test the Haiku version of BFS – on R5, but the latest binary file is known to have bugs. Where can I find a recent build of BFS to test?
look at the date … 05/28/2003 … That is what I was talking about. This is known to have bugs that have been fixed. It is no use testing an old version. We need a recent build.
Visit the Build Factory and get the Haiku-Distro-x86.tgz. In it you find always the current version from cvs.
It’s still beta, so handle with care and don’t risk you working system without backup!
The Build Factory downloads section is “Currently Unavailable”. Any alternatives? I really would like to test the latest stable version.
Thanks,
Prog.
Prognathous wrote:
The Build Factory downloads section is "Currently Unavailable". Any alternatives? I really would like to test the latest stable version.Thanks,
Prog.
BFS in SVN no longer works on R5, and probably never will again. It is now targeted only to Haiku.
What happened to binary compatibility and the modular R5<->Haiku concept?
Prog.
Prognathous wrote:
What happened to binary compatibility and the modular R5<->Haiku concept?Prog.
Nothing, but R5 has bad bad caching bugs that Axel has fixed in the Haiku version, but that make it incompatible with R5.
Haiku R1 is not meant to be compatible with R5’s bugs, except where totally needed… its not needed there.
Interesting stuff. Is there an editorial about this?
Prog.
Prognathous wrote:
Interesting stuff. Is there an editorial about this?Prog.
Err, no… the desire for documentation that users have is never met by the time or willingless of developers. Axel explained the binary compatibility split in a CVS log message…
I’d say this is significant news (not to say “focus shift” 
). Surely more people would be interested to know about this. This is exactly the kind of stuff that should be on the Haiku Newsletter.
Prog.
It’s not major news. Haiku will still be binary compatible. But the fact that Haiku has a different kernel means some bits of Haiku will only work in Haiku. AFAIK, being able to replace component-by-component in R5 was never a goal, just a useful side effect of the binary compatibility goal for some kits that aren’t too tied up to the kernel.