Linked by Thom Holwerda on Fri 20th Aug 2010 21:40 UTC, submitted by koki
BeOS & Derivatives This summer, too, the Haikuproject is part of the Google Summer of Code event. One of the more interesting projects is the Services Kit (draft document!) by Christophe "Shusui" Huriaux, which is an API to facilitate the creation of native web-enabled programs using standard web protocols and data exchange mechanisms.
Thread beginning with comment 437677
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Forward thinking
by kaiwai on Sat 21st Aug 2010 10:18 UTC in reply to "RE[2]: Forward thinking"
kaiwai
Member since:
2005-07-06

Indeed. And several GPL pieces have even been replaced in favor of BSD-licensed code (such as several network drivers, etc.)

It will be nice to release Haiku from glibc eventually as well ;)


I was under the impression that Haiku was still using the FreeBSD libc except that there were a couple of functions that were changed so that they operate like the glibc implementation rather than the FreeBSD implementation.

Reply Parent Score: 2

RE[4]: Forward thinking
by umccullough on Sat 21st Aug 2010 15:11 in reply to "RE[3]: Forward thinking"
umccullough Member since:
2006-01-26

I was under the impression that Haiku was still using the FreeBSD libc except that there were a couple of functions that were changed so that they operate like the glibc implementation rather than the FreeBSD implementation.


I believe they started off with the BSD libc, but switched to glibc for compatibility reasons (since BeOS had used glibc for its "libroot" support).

http://dev.haiku-os.org/browser/haiku/trunk/src/system/libroot/posi...

Recent discussion suggests that glibc may still be retained only for the BeOS compatibility (i.e. a gcc2-compiled set of libs will still remain optionally-installed for BeOS compatibility) while a non-GPL libc replacement will be grafted in moving forward.

Reply Parent Score: 3

RE[5]: Forward thinking
by kaiwai on Sun 22nd Aug 2010 01:45 in reply to "RE[4]: Forward thinking"
kaiwai Member since:
2005-07-06

I believe they started off with the BSD libc, but switched to glibc for compatibility reasons (since BeOS had used glibc for its "libroot" support).

http://dev.haiku-os.org/browser/haiku/trunk/src/system/libroot/posi...

Recent discussion suggests that glibc may still be retained only for the BeOS compatibility (i.e. a gcc2-compiled set of libs will still remain optionally-installed for BeOS compatibility) while a non-GPL libc replacement will be grafted in moving forward.


Sounds awesome; I have to admit though, it is rather disappointing that they've removed the progress chart which used to track the 'completeness' of each API call or feature; is there some way to track how far along they are in terms of implementation? do they have a goal for the final R1 release or is it more a situation of plodding along and focusing on the quality rather than an arbitrary time table?

Reply Parent Score: 2

RE[5]: Forward thinking
by Fettarme H-Milch on Sun 22nd Aug 2010 16:36 in reply to "RE[4]: Forward thinking"
Fettarme H-Milch Member since:
2010-02-16

glibc may still be retained only for the BeOS compatibility (i.e. a gcc2-compiled set of libs will still remain optionally-installed for BeOS compatibility) while a non-GPL libc replacement will be grafted in moving forward.

glibc isn't under GPL.

Reply Parent Score: 2