From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PIsqh-0004fe-Jd for garchives@archives.gentoo.org; Thu, 18 Nov 2010 00:59:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 979B1E06E8; Thu, 18 Nov 2010 00:59:07 +0000 (UTC) Received: from mail-ey0-f181.google.com (mail-ey0-f181.google.com [209.85.215.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 51560E06E8 for ; Thu, 18 Nov 2010 00:59:07 +0000 (UTC) Received: by eyb6 with SMTP id 6so1899730eyb.40 for ; Wed, 17 Nov 2010 16:59:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=W3arwpljXDSzkxcszt4kBy0Hy9YDfNRvPOv9HiJJ8WA=; b=bhm6AwOYDHNaD5TrrC4Nimt66+jEsv786zdpYm9WaHvNmiynqBTUzRLcJlMI9WYzHs Cc/vZX1uiDPdVF2EMcQoHcO4h6FyKTP/dDjH9et4lLYiFFr1MEWvEyE6Cn8p90WodvCo JNtQnwG1xMKTDAW073lw90oJ9RlLgtqESJgcM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=rcV6vU6AR8yFYkab5WD/xMMtSLZxlXZenKQexiFIh8x+epUlG6it2M8utsM+yhcbXs c244bxvFUPlDTXZ7bVZlUGE9kyea3Z79UDX8ZWDVRcjFE7de3czWhC4ESFiANpm5JB/I w1B6+UGzIN08/AkY02Z37EjKB6Ns5PbVaTMzA= Received: by 10.14.124.201 with SMTP id x49mr7460287eeh.7.1290041946711; Wed, 17 Nov 2010 16:59:06 -0800 (PST) Received: from nazgul.localnet (196-210-238-14.dynamic.isadsl.co.za [196.210.238.14]) by mx.google.com with ESMTPS id v56sm2842510eeh.20.2010.11.17.16.59.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 17 Nov 2010 16:59:05 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: How to configure thochpad sensitivity (using hal)? Date: Thu, 18 Nov 2010 02:59:32 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.36-ck; KDE/4.5.3; x86_64; ; ) References: <201011170200.49241.alan.mckinnon@gmail.com> <20101118004329.GB23732@waltdnes.org> In-Reply-To: <20101118004329.GB23732@waltdnes.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011180259.33235.alan.mckinnon@gmail.com> X-Archives-Salt: a850c331-11ec-4fa9-8d72-2764e7e8e94f X-Archives-Hash: 76b41f66b2ca4b982cb6ae5fffe7675c Apparently, though unproven, at 02:43 on Thursday 18 November 2010, Walter Dnes did opine thusly: > On Wed, Nov 17, 2010 at 02:00:48AM +0200, Alan McKinnon wrote > > > If you then mentioned that their defaults broke Dale's setup, they'd > > likely answer "Who's Dale?" followed shortly by "None of us have > > hardware like Dale to test. Sorry 'bout that. Set USE=-hal" > > Of course the USE flag advice is given *AFTER* the new flag breaks > your system. That's why I use "-*" at the beginning of my USE in > /etc/make.conf. I never found out whether hal would break my system. > If Dale had used "-*" his X would not have broken, even if some other > ebuild pulled it onto the machine as a hard-coded dependancy. Looks like the *actual* problem is non-application of OYFEAL[1],not what the devs do. Dale should have seen a new package being installed - an "N" inside "[ ]", should have seen new flags highlighted in colour, and should have decided. If he decided to go without hal, nothing would have changed for him. He decided to go with hal, and he got the breakage he did. Either way, seeing the USE flag changes tells him nothing about the impending breakage. He can only know that by *doing it*, or reading about others that did it. Let's look at this sanely and realise that there's nothing magic about hal and what it did. It has bugs. Big deal. So did jpeg and look at the carnage that one caused. How would your method of handling USE have assisted in preventing that breakage? Please note that the breakage in jpeg is much *much* more common than changes to default USE. -- alan dot mckinnon at gmail dot com