From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] package.mask-ed ebuilds
Date: Fri, 9 Apr 2010 15:13:31 -0400 [thread overview]
Message-ID: <20100409191331.GH1229@halcy0n.com> (raw)
In-Reply-To: <s2y8b4c83ad1004090010l905d38efge4243cecf0ece63a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Nirbheek Chauhan <nirbheek@gentoo.org> said:
> 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?
Just use some common sense. If its completely broken, it obviously
doesn't belong in the tree. If its something that somewhat works and is
actively being worked on, then its probably safe to add it and
package.mask it, with the intent that you are working towards getting it
to a state that it will be unmasked.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-04-09 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 7:10 [gentoo-dev] package.mask-ed ebuilds Nirbheek Chauhan
2010-04-09 9:53 ` Krzysztof Pawlik
2010-04-09 19:11 ` [gentoo-dev] " Ryan Hill
2010-04-09 19:13 ` Mark Loeser [this message]
2010-04-09 19:22 ` [gentoo-dev] " 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=20100409191331.GH1229@halcy0n.com \
--to=halcy0n@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