From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F3DB5138262 for ; Tue, 17 May 2016 15:34:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FFF21424F; Tue, 17 May 2016 15:34:23 +0000 (UTC) Received: from wp260.webpack.hosteurope.de (wp260.webpack.hosteurope.de [80.237.133.29]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3555114215 for ; Tue, 17 May 2016 15:34:21 +0000 (UTC) Received: from p549a9bce.dip0.t-ipconnect.de ([84.154.155.206] helo=gentp.lnet); authenticated by wp260.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1b2h0l-0006GD-Ue; Tue, 17 May 2016 17:34:20 +0200 Received: from gentp.lnet (gentp.lnet [IPv6:::1]) by gentp.lnet (Postfix) with ESMTP id 0EEE2260047 for ; Tue, 17 May 2016 17:34:19 +0200 (CEST) Date: Tue, 17 May 2016 17:34:18 +0200 From: Luis Ressel To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Proposal for changes for the next EAPI version Message-ID: <20160517173418.168d2cba@gentp.lnet> In-Reply-To: References: <20160516183840.4b241463@gentp.lnet> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; x86_64-pc-linux-gnu) 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=US-ASCII Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;aranea@aixah.de;1463499262;dff0ac97; X-Archives-Salt: 7e8bb4d1-b442-4e4e-b37e-e9485f4c5fcb X-Archives-Hash: 9d88ffe4946c22c67a76e91f8b8e3b44 On Tue, 17 May 2016 13:07:43 +0530 Pallav Agarwal wrote: > Tests run in src_test are provided by upstream, and does not > guarantee that a package that has been merged will actually run on > the system. If the maintainer could add a couple small scripts to > check basic functionality of the merged package, it would make > testing for arch testers much easier and reliable. Automated post-merge tests sound kinda dangerous to me. And I don't think there's any stipulation about src_test() only running upstream-provided test suites. IMHO, src_test() would be a good place for most of the maintainter-provided tests you have in mind. Of course, there are some possible tests for which the src_test() environment isn't suitable (because they're either interactive or really need to run post-merge), I just don't expect there'd be many of them. Therefore, I think we'd be better off providing such tests out-of-band (test plans in the wiki), or perhaps stuffing them into pkg_config(). Don't get me wrong, I'm not at all opposed to your idea of easing the ATs' life, I'm just not convinced of the neccessity of EAPI changes. :) -- Regards, Luis Ressel Luis Ressel GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD