# Hans de Graaff (8 Mar 2015)
# Mask various ruby19-only packages for removal.
#
# Failing tests with ruby20 due to encoding issues
dev-ruby/compass:0
# Old slots that are no longer in use
dev-ruby/jquery-rails:0
dev-ruby/simplecov:0
dev-ruby/simplecov-html:0
dev-ruby/sprockets:2.1
# Upstream indi
Some ebuilds in portage for Qt-based software support both Qt4 as well
as Qt5. Some have "+qt4 qt5" in IUSE, others have "qt4 qt5".
Is there a guideline for this somewhere? If a package needs Qt and thus
lists:
REQUIRED_USE="^^ ( qt4 qt5 )"
but otherwise doesn't prefer one version over the
On Sun, 2015-03-08 at 21:31 +0200, Nikos Chantziaras wrote:
> Some ebuilds in portage for Qt-based software support both Qt4 as well
> as Qt5. Some have "+qt4 qt5" in IUSE, others have "qt4 qt5".
>
> Is there a guideline for this somewhere? If a package needs Qt and thus
> lists:
>
>REQUIRE
On 08/03/15 21:35, Alexandre Rostovtsev wrote:
On Sun, 2015-03-08 at 21:31 +0200, Nikos Chantziaras wrote:
Some ebuilds in portage for Qt-based software support both Qt4 as well
as Qt5. Some have "+qt4 qt5" in IUSE, others have "qt4 qt5".
Is there a guideline for this somewhere? If a package ne
Am Sonntag, 8. März 2015, 21:50:02 schrieb Nikos Chantziaras:
> On 08/03/15 21:35, Alexandre Rostovtsev wrote:
> > On Sun, 2015-03-08 at 21:31 +0200, Nikos Chantziaras wrote:
> >> Some ebuilds in portage for Qt-based software support both Qt4 as well
> >> as Qt5. Some have "+qt4 qt5" in IUSE, other
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2015-03-08 23:59 UTC.
Removals:
net-misc/vidalia2015-03-03 22:14:20 blueness
x11-plugins/wmauda 2015-03-04 17:53:27 voyageu
Hi all,
Amongst Git migration preparations, one of the previously mentioned
items was that GitHub's webhooks were very useful for many tasks.
The QA team is already using them on the gentoo-portage-rsync-mirror
repo, to trigger regular Travis-CI runs.
In line with our policies of not depending o
