How it's listed in the library lists is up to the gil maintainers and you.
Since, I'm the maintainer I think it's just fine when gil::io is not listed. But I like to add a notice in the release notes that the old gil::io has been replaced.
Sure. You probably should also add your name to maintainers.txt, possibly as a separate entry there.
I have added all the missing notices, removed tab characters, and missing newlines for boost::gil.
I've updated the report: http://boost.cowic.de/rc/docs-inspect-trunk.html#gil
I would need some help here to hook up gil::io test with general boost testing.
I'd normally just include it from the gil tests (using 'build-project' I think). But if you want it to be separate you can add it to 'status/Jamfile.v2'. I think you'll also need to add an empty 'sublibs' file in 'libs/gil/' to indicate that it has sub-libraries - you can see these in the algorithm, functional, numeric, spirit and utility libraries.
I like to test that first on my machine. What would be the command line to build all boost test suits?
I think you just run 'b2' from the status directory.
gil::io has some compiler symbols to turn off reading from hard drive and writing to hard drive. I though that might be helpful for regression test servers that have limited capacities. When all tests are enabled there are 300 files written and like 500 files read. Also I don't wanna get into licensing issues for some of the test images I'm using.
You could ask about that on the testing list.