From: Tobias Klausmann <klausman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Can ATs add missing test deps?
Date: Mon, 6 Jun 2016 10:22:01 +0200 [thread overview]
Message-ID: <20160606082200.GA105497@skade.schwarzvogel.de> (raw)
Hi!
It happens every now and then that during ATing, I find that
USE=test should pull in extra deps. This usually is an easy and
not exactly controversial fix.
What's the hive mind's opinion on letting ATs add such deps if:
- Only one level deep, but multiple first-level deps are ok
- The deps themselves are already marked arch/~arch to the same
level as the package needing them*
- The deps themselves are not humunguous when it comes to
compile/test times.
* And by this I mean *all* arch/~arch keywords the base package
has, not just the one(s) the AT currently cares about.
Thoughts?
Regards,
Tobias
--
panic("floppy: Port bolixed.");
linux-2.2.16/include/asm-sparc/floppy.h
next reply other threads:[~2016-06-06 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 8:22 Tobias Klausmann [this message]
2016-06-06 10:36 ` [gentoo-dev] Can ATs add missing test deps? Alexis Ballier
2016-06-06 13:09 ` Dirkjan Ochtman
2016-06-06 19:08 ` Andreas K. Huettel
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=20160606082200.GA105497@skade.schwarzvogel.de \
--to=klausman@gentoo.org \
--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