public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Zack Weinberg <zackw@panix.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: RFC: deprecate sys/sysmacros.h inclusion from sys/types.h
Date: Fri, 19 Feb 2016 20:56:00 -0000	[thread overview]
Message-ID: <20160219205603.GM19841@vapier.lan> (raw)
In-Reply-To: <20151229224539.GL25803@vapier.lan>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

On 29 Dec 2015 17:45, Mike Frysinger wrote:
> On 29 Dec 2015 13:56, Zack Weinberg wrote:
> > On Tue, Dec 29, 2015 at 12:42 PM, Mike Frysinger wrote:
> > > On 18 Nov 2015 23:13, Zack Weinberg wrote:
> > >> Andreas may still be running whole-distro rebuild tests, but enough
> > >> results came back that I feel fairly confident saying that option B
> > >> (remove the #include <sys/types.h> from stdlib.h) is a non-starter.
> > >> There are too many (sloppily coded, yes) programs that include stdlib.h
> > >> and expect it to expose all the POSIX foo_t types.  That leaves us with
> > >> option A (remove the #include <sys/sysmacros.h> from sys/types.h) and
> > >> even that is going to break stuff.  So we need a deprecation period.
> > >
> > > i'm just going to drop it in Gentoo and let people fix the build failures
> > 
> > Well, if you're going to do that, option B might be better (or both!)
> > but I don't see it as a viable approach for upstream...
> 
> one at a time :).  the impact of sysmacros.h is significantly lower than
> the impact of sys/types.h.  although people have been building Gentoo
> against other C libs, so we are prob better protected against that.

i've deployed this in Gentoo now, but only to limited testers.
i'll open it up when glibc-2.22 goes stable in like ~30 days.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-19 20:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 14:21 RFC: remove <sys/sysmacros.h> from <sys/types.h> Zack Weinberg
2015-11-13 14:29 ` Zack Weinberg
2015-11-13 14:45 ` Dmitry V. Levin
2015-11-13 15:59   ` Paul Eggert
2015-11-13 23:43 ` Roland McGrath
2015-11-14  9:18   ` Andreas Schwab
2015-11-14 20:41     ` Zack Weinberg
2015-11-14 21:59       ` Rich Felker
2015-11-14 22:19         ` Andreas Schwab
2015-11-21  0:19           ` Roland McGrath
2015-11-21  0:56             ` Zack Weinberg
2015-11-14 20:19 ` Carlos O'Donell
2015-11-19  4:13 ` RFC: deprecate sys/sysmacros.h inclusion from sys/types.h Zack Weinberg
2015-12-07 14:03   ` Zack Weinberg
2015-12-21 20:31     ` Zack Weinberg
2016-01-11 15:16       ` Zack Weinberg
2016-01-11 15:27         ` Carlos O'Donell
2016-01-11 18:02           ` Zack Weinberg
2016-01-11 20:50             ` Carlos O'Donell
2015-12-29 20:42   ` Mike Frysinger
2015-12-29 21:56     ` Zack Weinberg
2015-12-29 22:45       ` Mike Frysinger
2016-02-19 20:56         ` Mike Frysinger [this message]
2016-04-20 17:37   ` Mike Frysinger
2016-04-20 17:58     ` Zack Weinberg
2016-04-20 18:11       ` Mike Frysinger
2016-04-21 19:31   ` Roland McGrath
2016-04-21 21:00     ` Zack Weinberg
2016-04-21 21:11       ` Roland McGrath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160219205603.GM19841@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=zackw@panix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).