The users.txt file bitrots over time. Here's an update.
2020-02-22 Bruno Haible
users.txt: Update.
* users.txt: Update URLs to projects that have moved or switched to git.
Use canonical host names. Prefer gitweb over cgit. Prefer the tree view
over the summary
Benno Fünfstück wrote:
> distributions also sometimes need to run gnulib-tool as part
> of a the build of a package (if the release tarball does not contain
> the required gnulib files or building directly from a git source if
> there is no release). In that case, it makes sense to have a package
>
Richard W.M. Jones wrote on 2013-09-23:
> The specific pain point for me is narrower than this however:
>
> Currently it does not seem to be possible to specify (in gnulib-tool)
> that you want only --lgpl=2 modules for one part of a project and
> don't care less about the modules used by another
2020-02-22 Bruno Haible
users.txt: Add groff.
Reported by Bjarni Ingi Gislason .
* users.txt: Add groff.
diff --git a/users.txt b/users.txt
index 5722dcc..803576c 100644
--- a/users.txt
+++ b/users.txt
@@ -29,6 +29,7 @@ The following packages appear to be using gnulib a
These are split from fchmodat, fchownat. GNU Emacs needs the
POSIX-specified fchmodat, but not the gnulib-specified chmodat and
lchmodat. Split the latter two into a new module chmodat.
Similarly for fchownat. This the same basic idea for why statat
was split from fstatat on 2013-01-23.
* lib/ch
Paul Eggert wrote:
> These are split from fchmodat, fchownat. GNU Emacs needs the
> POSIX-specified fchmodat, but not the gnulib-specified chmodat and
> lchmodat. Split the latter two into a new module chmodat.
As this is a backward-incompatible change for the gnulib users, we
should advertise i
Here comes the first part: the 'restrict' in the POSIX function declarations.
Note that the POSIX declarations of posix_spawn and posix_spawnp [1] are
incorrect: They lack a 'restrict' for the file_actions argument.
[1] https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_spawn.html
> 2020-02-16 Bruno Haible
>
> lchmod: Make more future-proof.
> * m4/lchmod.m4 (gl_FUNC_LCHMOD): Define NEED_LCHMOD_NONSYMLINK_FIX.
> (gl_PREREQ_LCHMOD): New macro.
> * lib/lchmod.c (orig_lchmod): New function.
> (lchmod): Test NEED_LCHMOD_NONSYMLINK_FIX. Access /p
Hi Paul,
> + if (S_ISLNK (st.st_mode))
> +{
> + close (fd);
> + errno = EOPNOTSUPP;
> + return -1;
> +}
Why EOPNOTSUPP? Why not ENOTSUP?
On Solaris, gnulib's lchmod on a symbolic link produces
lchmod: Operation not supported on transport endpoint
"transport endpoint" is
On 2/22/20 5:35 PM, Bruno Haible wrote:
Why EOPNOTSUPP? Why not ENOTSUP?
glibc will use EOPNOTSUPP, because POSIX says fchmodat with AT_SYMLINK_NOFOLLOW
uses EOPNOTSUPP in this situation.
11 matches
Mail list logo
