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 1LtU2c-0007Aa-NJ for garchives@archives.gentoo.org; Mon, 13 Apr 2009 21:50:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 37806E0474; Mon, 13 Apr 2009 21:50:09 +0000 (UTC) Received: from smtprelay11.ispgateway.de (smtprelay11.ispgateway.de [80.67.29.28]) by pigeon.gentoo.org (Postfix) with ESMTP id 0DB6FE0474 for ; Mon, 13 Apr 2009 21:50:09 +0000 (UTC) Received: from [85.179.2.185] (helo=[192.168.0.3]) by smtprelay11.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LtU2a-0001BM-6i for gentoo-dev@lists.gentoo.org; Mon, 13 Apr 2009 23:50:08 +0200 Message-ID: <49E3B38F.1020003@hartwork.org> Date: Mon, 13 Apr 2009 23:50:07 +0200 From: Sebastian Pipping User-Agent: Thunderbird 2.0.0.19 (X11/20090216) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] `paludis --info' is not like `emerge --info' References: <20090218232212.5452b86d@epia.jer-c2.orkz.net> <20090218225506.14b91815@snowcone> <20090404151730.55b89242@gentoo.org> <49E32E51.60204@hartwork.org> <20090413132938.14c426e5@snowcone> In-Reply-To: <20090413132938.14c426e5@snowcone> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Df-Sender: 874396 X-Archives-Salt: cce87040-df6b-406a-b5eb-780b58597e5c X-Archives-Hash: 148f65dd813057c6a08e5016826fc10a Ciaran McCreesh wrote: > Taking any of it out would be > removing things that are required to determine the cause of a bug. I doubt that's true in most cases: The information needed to finding the bug is a (possibly small) subset of the whole. I don't see how additionally providing a stripped down version of paludis info hurts anybody, as the subset either holds what the wrangler needs or it doesn't, in which case they can still request more information for the reporter. I suggest that you take this as a usability request from the users of your software. Isn't that a great chance to make several people happier every day in the future by just a few lines of code on your end? Would they raise their voice if it did not matter? Sebastian