mirror of
https://https.git.savannah.gnu.org/git/gnulib.git
synced 2026-05-13 15:13:36 +00:00
295cc7fb37
Most of these were reported by Josh Soref <jsoref@gmail.com> in: https://lists.gnu.org/r/bug-gnulib/2023-06/msg00057.html except that some are omitted because the original is OK (e.g., "obsolescent"), and some are omitted because they are upstream files and I've fixed them upstream or have filed bug reports, and I made a few nearby corrections to grammar.
128 lines
4.2 KiB
Plaintext
128 lines
4.2 KiB
Plaintext
Status for libposix
|
|
===================
|
|
|
|
This file documents the status of work-in-progress.
|
|
No ChangeLog entries are needed for this file.
|
|
|
|
Status for the libposix branch
|
|
------------------------------
|
|
|
|
Bruce Korb says:
|
|
|
|
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.
|
|
|
|
|
|
TODO list for master
|
|
--------------------
|
|
|
|
Bruno Haible says:
|
|
|
|
1) ... 7)
|
|
proposed by Gary in the thread starting at
|
|
[PATCH 0/7] contents of topic/libposix for merge to master
|
|
in <https://lists.gnu.org/r/bug-gnulib/2010-10/threads.html>
|
|
|
|
1) Allow generate header files to coexist without shadowing each other.
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00283.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00289.html>
|
|
|
|
Still missing: dealing with include_next and old compilers, cf.
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00269.html>
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00285.html>
|
|
|
|
2) Allow using libgnu's file name in module descriptions.
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00284.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00291.html>
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00308.html
|
|
|
|
3) iconv_open's file list
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00282.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00290.html>
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00307.html>
|
|
libposix needs to install only selected headers, not all of them. Let the
|
|
script look at the 'Include:' section of each module description.
|
|
|
|
4) Module libposix
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00280.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00292.html>
|
|
More discussion needed
|
|
|
|
5) Installable headers
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00281.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00293.html>
|
|
Patch to be rewritten to use nobase_nodist_include_HEADERS,
|
|
also need to add an Automake conditional to distinguish libposix from
|
|
other projects.
|
|
Also see whether the Automake bug can be fixed.
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00325.html>
|
|
|
|
6) libposix subdirectory
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00277.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00294.html>
|
|
|
|
7) use git-version-gen for version numbering
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00279.html>
|
|
|
|
Discussion:
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00297.html>
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-10/msg00303.html>
|
|
Patch to be revised.
|
|
|
|
8) Licensing
|
|
<https://lists.gnu.org/r/bug-gnulib/2010-12/msg00184.html>
|
|
|
|
Status: A majority of the issues have been handled.
|
|
Obsolete modules (free, memcpy) can be ignored.
|
|
To be done:
|
|
getcwd
|
|
faccessat
|
|
fdopendir
|
|
linkat
|
|
mkfifoat
|
|
openat
|
|
readlinkat
|
|
renameat
|
|
symlinkat
|
|
utimensat
|
|
|
|
9) Versioning
|
|
<https://lists.gnu.org/r/bug-gnulib/2011-01/msg00163.html>
|
|
|
|
Status: No real plan exists.
|