On 05/03/11 15:45, Reuben Thomas wrote:
Is there a public todo for the libposix branch? If so, could it go in
the branch somewhere visible? If not, is there any way I can help
gather up the material for one? I'm keen now to see libposix a
reality, so I'd like to see what still needs to be done to get it in
master.
I think a real big step in libposix is to get a little experience with it.
There are also some few little nits pointed out in the discussions that
need some careful consideration, but some experience in using it would
be good, too. The intended/expected usage is along the lines of:
1. configure, build and install the thing. Perhaps from:
http://autogen.sourceforge.net/data/
or roll your own, but the distribution should be there, I think.
2. fiddle a project to detect that it is "sufficiently recent" to
cover the needs of this unnamed project. That is an interesting
issue, though: the concept behind "configure" is that you do
feature tests rather than version testing. However, if you choose
to not test the version of libposix and test the features you
need of libposix, then I have an extremely difficult time trying
to understand the point of libposix -- you are back to running
a bunch of feature tests that take too long. Testing for a
libposix current as of some marker (version number or date)
seems right to me, though there are some caveats to consider
regarding "retired" POSIX features.
Anyway, the "fiddle a project" should boil down to testing
for libposix in some way and then dying if it is not up to snuff.
3. configure, build, test, install and test installation of said project.
I've done this with a tiny example project I have, but I do not
have access to a wide variety of platforms (Gary?).
Thank you for your interest! With nobody having tested the distro tarball,
it becomes a lower priority thing for me. :)
Cheers - Bruce
