From owner-freebsd-current Fri Mar 8 10:45:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id D0C4A37B405; Fri, 8 Mar 2002 10:45:23 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g28IjENH134648; Fri, 8 Mar 2002 13:45:14 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020308161716.GA65905@leviathan.inethouston.net> References: <20020308145953.GA62875@leviathan.inethouston.net> <20020308161716.GA65905@leviathan.inethouston.net> Date: Fri, 8 Mar 2002 13:45:13 -0500 To: "David W. Chapman Jr." , Robert Watson From: Garance A Drosihn Subject: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) Cc: "David W. Chapman Jr." , Murray Stokely , developers@FreeBSD.ORG, current@FreeBSD.ORG, re@FreeBSD.ORG, portmgr@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:17 AM -0600 3/8/02, David W. Chapman Jr. wrote: >Yes. Recent changes to netinet/in.h have made it require the >inclusion of arpa/inet.h. As well, arpa/inet.h must include >netinet/in.h. IOW, each of these files must #include the >other in order to work correctly. > >As you might guess, this is a less than desirable situation. >[A #includes B] and [B #includes A] is a very bad arrangement. >However, unless both files are overhauled, that is what will >have to happen. > >To say that this sucks is an understatement. [...] >Since the problem is a large one, and any change will not >happen without a reasonable amount of deliberation, I suggest >you submit a PR with a patch for kdelibs source tree. Mike Barcroft, Bruce Evans, and maybe a few others are working on an update to about eight different include files which should clear up many of these issues. I think it would be very desirable to get this include-file-cleanup patch committed before the snapshot is done. The present version of this patch clears up a lot of the compile-time warnings that come up when doing a buildworld of current, but it still isn't quite right. If this current snapshot means more people will be running current, then I'd hate to see them chasing after compile-time warnings which are due to the present state of the system include files... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message