> but it's not a question of forking the library. there's a ton of stuff > under go/src, > so what makes libbio special?
I'm not sure where the wires get crossed, let's see if I can get my point across or, alternatively, if I can figure out what I'm missing. In building the Go tool chain, in Plan 9, only libmach, of the libararies required, differs substantially from the Go release version to require special functionality. The differences aren't irreconcilable, but they are pretty vast. For a more Posix-y environment, lib9 and libbio are also required to provide features that Plan 9 has natively. Lib9 mirrors libc and libbio is analogous to "the real thing". My contention is that we ought to keep these differences to an absolute minimum and, specifically, we ought to avoid libbio diverging from the Plan 9 native version - at the cost of altering the latter, if necessary - so that the two systems are kept closer together. The point here is that once we grant licence for libbio to diverge, there is no limit to how far it will go and any efforts to bring either in line with the other will be as difficult as it would be now for libmach. Libmach and lib9 both show how far apart this divergence will go if encouraged. It is moot, I grant that, but as a responsible citizen, I feel it is my duty not to create conditions than future generations can't recover from, at least as long as there is an option. Yeah, it's a philosophical line in the sand, but you did ask where I was drawing it and I'm hoping I have made it a little clearer (even to myself). ++L
