* Michael Kerrisk:
I'm not sure I'd view the glibc position quite so harshly (although
it is disappointing to me that bug 6399 remains open). I think they
are simply short of people to work on this task. There was a lengthy
period where no syscall wrappers were being added (pretty much from
2.16 to 2.24, as far as I can tell), but that has changed.
People may have disappeared from glibc development who have objected to
gettid. I thought this was the case with strlcpy/strlcat, but it was
not.
At present, it takes one semi-active glibc contributor to block addition
of a system call. The process to override a sustained objection has
never been used successfully, and it is a lot of work to get it even
started.
Thanks,
Florian
On Sun, 11 Nov 2018, Florian Weimer wrote:
People may have disappeared from glibc development who have objected to
gettid. I thought this was the case with strlcpy/strlcat, but it was
not.
Well, I know of two main people who were objecting to the notion of adding
bindings for all non-obsolescent syscalls, Linux-specific if not suitable
for adding to the OS-independent GNU API, and neither seems to have posted
in the past year.
At present, it takes one semi-active glibc contributor to block addition
of a system call. The process to override a sustained objection has
never been used successfully, and it is a lot of work to get it even
started.
We don't have such a process. (I've suggested, e.g. in conversation with
Carlos at the Cauldron, that we should have something involving a
supermajority vote of the GNU maintainers for glibc in cases where we're
unable to reach a consensus in the community as a whole.)
--
Joseph S. Myers
joseph@codesourcery.com
On 11/12/18 11:43 AM, Joseph Myers wrote:
On Sun, 11 Nov 2018, Florian Weimer wrote:
quoted
People may have disappeared from glibc development who have objected to
gettid. I thought this was the case with strlcpy/strlcat, but it was
not.
Well, I know of two main people who were objecting to the notion of adding
bindings for all non-obsolescent syscalls, Linux-specific if not suitable
for adding to the OS-independent GNU API, and neither seems to have posted
in the past year.
quoted
At present, it takes one semi-active glibc contributor to block addition
of a system call. The process to override a sustained objection has
never been used successfully, and it is a lot of work to get it even
started.
We don't have such a process. (I've suggested, e.g. in conversation with
Carlos at the Cauldron, that we should have something involving a
supermajority vote of the GNU maintainers for glibc in cases where we're
unable to reach a consensus in the community as a whole.)
... and I need a good excuse to propose such a process :-)
--
Cheers,
Carlos.