From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] package.mask-ed ebuilds
Date: Fri, 9 Apr 2010 12:40:50 +0530 [thread overview]
Message-ID: <s2y8b4c83ad1004090010l905d38efge4243cecf0ece63a@mail.gmail.com> (raw)
Hello!
So, I can't find any documentation about this; nor can I find a
best-practices list. Can we add broken ebuilds in-tree as long as they
are package.masked? automagic deps, wrong deps, missing deps, file
collisions, etc etc? Even if it makes the ebuild completely unusable
by itself?
If yes:
So we can add completely broken and useless stuff to tree as long as
it's package.masked?
If no:
What's the minimum amount of "working-ness" that an ebuild must have
to be added to tree? Who decides this? The QA team?
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next reply other threads:[~2010-04-09 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 7:10 Nirbheek Chauhan [this message]
2010-04-09 9:53 ` [gentoo-dev] package.mask-ed ebuilds Krzysztof Pawlik
2010-04-09 19:11 ` [gentoo-dev] " Ryan Hill
2010-04-09 19:13 ` [gentoo-dev] " Mark Loeser
2010-04-09 19:22 ` Michał Górny
2010-04-09 19:34 ` Ben de Groot
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=s2y8b4c83ad1004090010l905d38efge4243cecf0ece63a@mail.gmail.com \
--to=nirbheek@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