> > well, it have to be so.. but if it breaks existing code, then it could > mean that libc turned from implicit caching/buffering to explicit one. > And this could mean many changes here and there. > (Besides of that, i never liked RemoteString and other things related > to writing to .changes file... > that code begs for proper rewrite)
The whole .changes and .source code is extremely complicated considering for
what it gets us.
Marcus
