public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pallav Agarwal <pallavagarwal07@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Proposal for changes for the next EAPI version
Date: Mon, 16 May 2016 18:13:33 +0530	[thread overview]
Message-ID: <CAK23ojRBAWH1OR2BiKfqLfZgoKraZd9T_HY-+j6gyS8tG+TUEg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1165 bytes --]

             reply	other threads:[~2016-05-16 12:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 12:43 Pallav Agarwal [this message]
2016-05-16 16:38 ` [gentoo-dev] Proposal for changes for the next EAPI version Luis Ressel
2016-05-17  7:37   ` Pallav Agarwal
2016-05-17  8:02     ` Kent Fredric
2016-05-17  8:46       ` Tobias Klausmann
2016-05-17  9:15         ` Kent Fredric
2016-05-17 10:57           ` Rich Freeman
2016-05-17 11:25             ` Pallav Agarwal
2016-05-17 11:42               ` Rich Freeman
2016-05-17 10:01         ` Pallav Agarwal
2016-05-17 11:26           ` Michael Orlitzky
2016-05-17 11:29             ` Ciaran McCreesh
2016-05-18  8:18               ` [gentoo-dev] " Duncan
2016-05-17 13:53     ` [gentoo-dev] " M.B.
2016-05-17 14:02       ` Brian Dolbec
2016-05-17 15:34     ` Luis Ressel
2016-05-17 16:05       ` Sébastien Fabbro
2016-05-17 16:42         ` Rich Freeman
2016-05-18  0:14         ` Kent Fredric
2016-05-18  0:35           ` M. J. Everitt
2016-05-18  0:44             ` Kent Fredric
2016-05-18  0:48               ` M. J. Everitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK23ojRBAWH1OR2BiKfqLfZgoKraZd9T_HY-+j6gyS8tG+TUEg@mail.gmail.com \
    --to=pallavagarwal07@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox