1Status for libposix 2=================== 3 4This file documents the status of work-in-progress. 5No ChangeLog entries are needed for this file. 6 7Status for the libposix branch 8------------------------------ 9 10Bruce Korb says: 11 12I think a real big step in libposix is to get a little experience with it. 13There are also some few little nits pointed out in the discussions that 14need some careful consideration, but some experience in using it would 15be good, too. The intended/expected usage is along the lines of: 16 171. configure, build and install the thing. Perhaps from: 18 http://autogen.sourceforge.net/data/ 19 or roll your own, but the distribution should be there, I think. 20 212. fiddle a project to detect that it is "sufficiently recent" to 22 cover the needs of this unnamed project. That is an interesting 23 issue, though: the concept behind "configure" is that you do 24 feature tests rather than version testing. However, if you choose 25 to not test the version of libposix and test the features you 26 need of libposix, then I have an extremely difficult time trying 27 to understand the point of libposix -- you are back to running 28 a bunch of feature tests that take too long. Testing for a 29 libposix current as of some marker (version number or date) 30 seems right to me, though there are some caveats to consider 31 regarding "retired" POSIX features. 32 33 Anyway, the "fiddle a project" should boil down to testing 34 for libposix in some way and then dying if it is not up to snuff. 35 363. configure, build, test, install and test installation of said project. 37 38 39TODO list for master 40-------------------- 41 42Bruno Haible says: 43 441) ... 7) 45 proposed by Gary in the thread starting at 46 [PATCH 0/7] contents of topic/libposix for merge to master 47 in <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/threads.html> 48 491) Allow generate header files to coexist without shadowing each other. 50 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00283.html> 51 52 Discussion: 53 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00289.html> 54 55 Still missing: dealing with include_next and old compilers, cf. 56 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00269.html> 57 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00285.html> 58 592) Allow using libgnu's file name in module descriptions. 60 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00284.html> 61 62 Discussion: 63 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00291.html> 64 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00308.html 65 663) iconv_open's file file list 67 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00282.html> 68 69 Discussion: 70 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00290.html> 71 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00307.html> 72 libposix needs to install only selected headers, not all of them. Let the 73 script look at the 'Include:' section of each module description. 74 754) Module libposix 76 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00280.html> 77 78 Discussion: 79 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00292.html> 80 More discussion needed 81 825) Installable headers 83 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00281.html> 84 85 Discussion: 86 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00293.html> 87 Patch to be rewritten to use nobase_nodist_include_HEADERS, 88 also need to add an Automake conditional to distinguish libposix from 89 other projects. 90 Also see whether the Automake bug can be fixed. 91 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00325.html> 92 936) libposix subdirectory 94 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00277.html> 95 96 Discussion: 97 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00294.html> 98 997) use git-version-gen for version numbering 100 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00279.html> 101 102 Discussion: 103 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00297.html> 104 <http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00303.html> 105 Patch to be revised. 106 1078) Licensing 108 <http://lists.gnu.org/archive/html/bug-gnulib/2010-12/msg00184.html> 109 110 Status: A majority of the issues have been handled. 111 Obsolete modules (free, memcpy) can be ignored. 112 To be done: 113 getcwd 114 faccessat 115 fdopendir 116 linkat 117 mkfifoat 118 openat 119 readlinkat 120 renameat 121 symlinkat 122 utimensat 123 1249) Versioning 125 <http://lists.gnu.org/archive/html/bug-gnulib/2011-01/msg00163.html> 126 127 Status: No real plan exists. 128