List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Fri, 9 Apr 2010 12:40:50 +0530
Nirbheek Chauhan <email@example.com> wrote:
> 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?
In my opinion, an ebuild should be added to the tree as long as it will
be useful to users. If your ebuild is WIP but you want to give some
users an option to already use it or get some feedback, you could
consider adding it.
Moreover, I wouldn't take dependency-related issues as a reason to mask
the ebuild. As long as it's not going to hurt users' system or (if it's
an version bump) replace working version with non-working one, it
doesn't need the mask.
So, it all depends on how useful the ebuild is, and how dangerous it
can become. If it just misses some polishes, it's acceptable -- as long
as you're going to maintain it and fix all the known issues ASAP.
Please notice that this is no official statement but only my personal
opinion on the topic.