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 1RXhaI-0002VS-4V for garchives@archives.gentoo.org; Mon, 05 Dec 2011 23:04:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AAA7221C111; Mon, 5 Dec 2011 23:04:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 77F7B21C10E for ; Mon, 5 Dec 2011 23:04:07 +0000 (UTC) Received: from [192.168.178.31] (e178073118.adsl.alicedsl.de [85.178.73.118]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: chithanh) by smtp.gentoo.org (Postfix) with ESMTPSA id 4C6B61B4017 for ; Mon, 5 Dec 2011 23:04:05 +0000 (UTC) Message-ID: <4EDD4DF3.60307@gentoo.org> Date: Tue, 06 Dec 2011 00:04:19 +0100 From: =?UTF-8?B?Q2jDrS1UaGFuaCBDaHJpc3RvcGhlciBOZ3V54buFbg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111031 Firefox/7.0.1 SeaMonkey/2.4.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 2011-12-13 References: <20111203103024.GN37825@gentoo.org> <201112050148.01078.vapier@gentoo.org> <4EDD4206.30707@gentoo.org> <201112051746.11995.vapier@gentoo.org> <4EDD4BE0.5090902@gentoo.org> In-Reply-To: <4EDD4BE0.5090902@gentoo.org> X-Enigmail-Version: 1.4a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 7edb1f44-8b98-46f4-af4f-f35d588d601e X-Archives-Hash: 9424be92fd246726c804a03fe23e433a Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85n schrieb: > Mike Frysinger schrieb: >> what would be more likely is they try to run=20 >> `cdrecord`, find it missing, find the build failed, and then file a bu= g. that=20 >> workflow really isn't affected by the defaults here. >> -mike >=20 > In versions prior to cdrecord-3.00 it was actually the case that nothin= g > at all was installed. That would cause patrick to notice and scroll bac= k > up in his terminal buffer now to see wtf went wrong. >=20 > Since 3.00 it installs a cdrecord binary that runs but doesn't actually > talk to hardware. Fun. Oh nevermind, I noticed it doesn't install cdrecord after all, and prefix uses system-installed one. Best regards, Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85n