From owner-freebsd-current Thu Oct 10 7:10:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BC9A37B401 for ; Thu, 10 Oct 2002 07:10:53 -0700 (PDT) Received: from volatile.chemikals.org (cae57-176-131.sc.rr.com [66.57.176.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEF6843EA9 for ; Thu, 10 Oct 2002 07:10:52 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.6/8.12.6) with ESMTP id g9AEApTe037297; Thu, 10 Oct 2002 10:10:51 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Thu, 10 Oct 2002 10:10:50 -0400 (EDT) From: Wesley Morgan To: Alex Zepeda Cc: Terry Lambert , Subject: Re: KDE 3.0 broken in current?? In-Reply-To: <20021010060428.GB751@blarf.homeip.net> Message-ID: <20021010100330.S37189-100000@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Wed, 9 Oct 2002, Alex Zepeda wrote: > I'm quite suprised how this managed to avoid detection for so long > (webcvs.kde.org indicated that the last commit to this branch was > 12 > months ago). It's that whole feeling of fixing the same problems over and > over again. Most likely this is a problem that was uncovered by some change in our headers. I've seen a lot of commits come down the pipes removing "unneeded" includes from one header or another... Which of course is the correct thing to do and it encourages better coding practices to make people put headers in the right order. > Admittedly I run development versions of both FreeBSD and KDE, and the > kde-freebsd team uses stable overwhelmingly so the combination doesn't > receive the testing that others do. Last I checked, Will was at the very least testing each release on -current. KDE is such a big package I can't imagine it being very popular with testers, although with the new GCC snapshot imported I will probably rebuilt it. Would it be possible to modify the bento cluster to have another slice with the minimal -current install, and (using boot0cfg, or modifying a GRUB boot menu) reboot into -current for an automated package build? Or maybe this is already done. -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message