There are a few things where the WvStreams-using programs just appear as if
they really wanted to just be subdirectories inside of WvStreams itself.
For example, wvver.h tying all of them together, in one big happy family.
Or WvStreams having the only configure script, the others just using the
results of that (which I think is even *installed*, which I don't think is
a good idea), and so on.
Original issue reported on code.google.com by pphaneuf on 7 Mar 2007 at 9:57
Original issue reported on code.google.com by
pphaneuf
on 7 Mar 2007 at 9:57