From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1K6NuM-0008E6-4Z for garchives@archives.gentoo.org; Wed, 11 Jun 2008 10:50:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 27859E01A6; Wed, 11 Jun 2008 10:50:23 +0000 (UTC) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by pigeon.gentoo.org (Postfix) with ESMTP id EE8EEE01A6 for ; Wed, 11 Jun 2008 10:50:22 +0000 (UTC) Received: by an-out-0708.google.com with SMTP id c28so713923ana.47 for ; Wed, 11 Jun 2008 03:50:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=Qybkgjb15qYAFGXaucHhChB1X9NnSE18+WPD+utrY/E=; b=wfVcqtkaQ6IV+W4TAzlQGH2/PzsGmEvzy7hgfoOvz1+RQs/+hlXot65PSI6O1V16JD 3OyJnHrv5sYZhr2MZVibQt220Wv4oYtbXfSoJqgQBaEVUUrXkaRhKRrQHEBoTFH/jWcn 3pPF9ZdH5tAchmPiB81AyFzLj29VAGVvOcyHM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=C8wkoroQRu0yFCEjvcPpenAqknbHycyHE4wbF1D8xHx5CUzBybUm0fQNriXGWL5g/c gFTdjN1/GW6j9CMG4juZaPb71WfzWksJpeEJCdF7VgcNkSY8vTAJRuCdTFwD9xiIYHzh ODygC7zcDU0QgorvVv00NzHY0ng/gD9WBtpcI= Received: by 10.100.122.8 with SMTP id u8mr7269841anc.103.1213181420720; Wed, 11 Jun 2008 03:50:20 -0700 (PDT) Received: by 10.100.11.12 with HTTP; Wed, 11 Jun 2008 03:50:19 -0700 (PDT) Message-ID: <3c32af40806110350v2735c537i3c3b136ad2c3375f@mail.gmail.com> Date: Wed, 11 Jun 2008 12:50:19 +0200 From: "Santiago M. Mola" Sender: cooldwind@gmail.com To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] EAPI-2 - Let's get it started In-Reply-To: <484F6851.8060804@gentoo.org> 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484EAB4F.6070608@gentoo.org> <200806110011.41718.zlin@gentoo.org> <20080611010347.6ced7db2@sheridan.genone.homeip.net> <200806110142.38384.zlin@gentoo.org> <484F5372.80301@gentoo.org> <20080611062006.5d517d71@googlemail.com> <484F6529.8000300@gentoo.org> <20080611064420.704765d4@googlemail.com> <484F6851.8060804@gentoo.org> X-Google-Sender-Auth: 27e7e7b8faa9183e X-Archives-Salt: 18147e83-b9f8-4f3f-adf5-77382fe40ffc X-Archives-Hash: ac32f2bad6a800f1933446ad92be66ca On Wed, Jun 11, 2008 at 7:53 AM, Luca Barbato wrote: >> >> A whole bunch of science packages have upstreams that say "If you're >> building from source, run 'make check' and if it fails don't carry on". > > Their rationale behind that is that their code is severely broken, using > experimental features from their language of choice or, simply, that they > are paranoid and couldn't think better ways to annoy people? > It's not as simple as that. A package may fail tests because compiler bugs, build environment misconfiguration, problems in a library which is being used, a setup problem or, of course, a bug in the package which shows up in rare cases and haven't been spoted by upstream yet. When the package can be critical for the system, upgrading to a buggy version will eat people's dogs. I feel a bit safer when I run the test phase for my package manager, and I wouldn't install it if it's failing any test. I don't think that's too paranoid. Also let's put a real example: gmplib. From www.gmplib.org on the front page: " IMPORTANT INFORMATION FOR ALL GMP USERS: GMP is very often miscompiled! We are seeing ever increasing problems with miscompilations of the GMP code. It has now come to the point where a compiler should be assumed to miscompile GMP. Please never use your newly compiled libgmp.a or libgmp.so without first running make check. If it doesn't complete without errors, don't trust the library. Please try another compiler release, or change optimization flags until it works. If you have the skill to isolate the problem, please report it to us if it is a GMP bug; else to the compiler vendor. (The compilers that cause problems are HP's unbundled compilers and GCC, in particular Apple's GCC releases.) " Upstream clearly states that a gmp build which tests have failed shouldn't be used. I bet they deny support for users who fail to follow that indication ;-) Regards, -- Santiago M. Mola Jabber ID: cooldwind@gmail.com -- gentoo-dev@lists.gentoo.org mailing list