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 4F11613825A for ; Mon, 16 May 2016 12:44:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9F90514255; Mon, 16 May 2016 12:43:54 +0000 (UTC) Received: from mail-vk0-f50.google.com (mail-vk0-f50.google.com [209.85.213.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AF4A621C04D for ; Mon, 16 May 2016 12:43:53 +0000 (UTC) Received: by mail-vk0-f50.google.com with SMTP id c189so58026922vkb.1 for ; Mon, 16 May 2016 05:43:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=6syrknVkpdZwt21p0+zomL/5jFGPNGkhtP9jXRkZe38=; b=L2S8X7iioa/4ZFyH8n6iwTa1FAQ68OQfC+McJpvFklgBE89O4gx+QByriPQz840g3S kRN+9Hl+mFSo+7JZL4n2Jiwgqj/kD2VflER015//bwax/t39nIaVzNR1CWTV3lzXjYzd wUsTlrh5ZCTfgFJKmGQZxqYTjBEkxZvEIIpoHyyNdDQLXawZQGPdvQZrmheAgS2assM2 8WDfyU587cpSLm+lD91696/qWdbEoe2a40CTgIYMYwpCr4R73mChyAYYtKXBlDA+PZYn agz8C8Chno1xPY6+98Eixis7cmFot0ikGWEPvp9Z4oH63w3da1CZGgXXSAYNyJeb7v4S GWXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6syrknVkpdZwt21p0+zomL/5jFGPNGkhtP9jXRkZe38=; b=d2pD4y6CIR/oe5xnkLkdUUeBbSeSSXBo4BOZ6gpHABmJtpig+0qyI2TPRb+yZMBj1N 7VUkLey1ZXn/j2S8RzFEcTdYAjKH5VuS/9S7v5vD36hAamPsMPWDXTuV+tnKaItaIdCm XUkUP1MckXkaIjs35X9/xU8SNHCJK1joOTjxoBw99kaKPM1iWjS5WNraSXdORaPjtCou b40A0Ue365UkTuN7x8YNGhY12zEm+PrSfEXMbkeyiM05XIEs6V1VJqZwFy69snkRcioX 7rpMBlnv1CszzB2kWRiuSater/zfPRqGhDY1Xj4gKlWQzxHeYErDYcJtfhDdvLtji6pw CITg== X-Gm-Message-State: AOPr4FWLv0i5HKha0nuqKD+777dDmNNhaus/uE5p3DMmm67G3aGCuo7TQOsMUm0M0d38DTrWURgPcynM7+oLGg== X-Received: by 10.159.39.231 with SMTP id b94mr15014867uab.64.1463402632762; Mon, 16 May 2016 05:43:52 -0700 (PDT) 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 Received: by 10.176.2.46 with HTTP; Mon, 16 May 2016 05:43:33 -0700 (PDT) From: Pallav Agarwal Date: Mon, 16 May 2016 18:13:33 +0530 Message-ID: Subject: [gentoo-dev] Proposal for changes for the next EAPI version To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary=94eb2c122e0616dc8f0532f4fa0c X-Archives-Salt: ad775a02-7ef5-4545-ab1e-6844171171c6 X-Archives-Hash: 138638c5e8977a0612b67db04988bbf7 --94eb2c122e0616dc8f0532f4fa0c Content-Type: text/plain; charset=UTF-8 Hi, I am a student selected for GSoC 2016. One of the things in my proposal requires the ebuilds to carry a mechanism to test the built software by running some script provided by the maintainer of the ebuild. This would be basically similar to whatever tests an Arch Tester would do, however made easier by the fact that it would be written by the maintainer. This could be to test whatever bug the ebuild fixes, or the basic functionality of the software. This would help to automate the stabilization of the built packages (which my project on continuous stabilization wishes to accomplish). What I'm suggesting is to add a new function post_install_test. The function will run only if the build is being run for stabilization (either as a part of automated stabilization, or manual) which can be controlled by a USE flag. The function would also require independent dependencies in case it uses external applications to test the one being built. I wanted to know other opinions on this matter. Thanks, Pallav Agarwal --94eb2c122e0616dc8f0532f4fa0c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,
I am a student selected for GSoC 2016. One of the = things in my proposal requires the ebuilds to carry a mechanism to test the= built software by running some script provided by the maintainer of the eb= uild.
This would be basically similar to whatever tests an Arch T= ester would do, however made easier by the fact that it would be written by= the maintainer.=C2=A0
This could be to test whatever bug the ebu= ild fixes, or the basic functionality of the software. This would help to a= utomate the stabilization of the built packages (which my project on contin= uous=C2=A0stabilization wishes to accomplish).

Wha= t I'm suggesting is to add a new function post_install_test. The functi= on will run only if the build is being run for stabilization (either as a p= art of automated stabilization, or manual) which can be controlled by a USE= flag. The function would also require independent dependencies in case it = uses external applications to test the one being built.

I wanted to know other opinions on this matter.

<= div>Thanks,
Pallav Agarwal
--94eb2c122e0616dc8f0532f4fa0c--