[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2017-04-30 23:59 UTC

/aunit 20170426-18:32 tupone e2658d94c1c dev-ada/aws 20170430-20:36 tupone 1526c880d20 dev-ada/gnatmem 20170425-19:52 tupone d8e663b26f5 dev-ada/gps-bin 20170430-17:27 tupone fa458aa29ce dev-python/asn1crypto 20170425

[gentoo-dev] [PATCH] app-portage/eclass-manpages: Add support for @DEFAULT-ASSUMED

From: Kent Fredric @DEFAULT-ASSUMED allows eclasses to document any implied value that internal code will assume when the ENV var is undefined. @DEFAULT-ASSUMED should typically be used in conjunction with @DEFAULT-UNSET, but it can be used in conjunction with either

[gentoo-dev] [PATCH] app-portage/eclass-manpages: Add support for @DEFAULT-VALUE

From: Kent Fredric @DEFAULT-VALUE allows eclasses to document the default values they will inject when eclass-to-manpage can't extract it. When eclass-to-manpage *can* extract it, it adds a warning when the extracted value is different from that declared, (but the declared

[gentoo-dev] [PATCH] app-portage/eclass-manpages: Add support for @OUTPUT

From: Kent Fredric @RETURNS is abused presently both as bash exit code values ( that is, bash return values ), and capturable STOUT values. This is problematic, as they're not equivalent: One is passed around via $? , and the other requires VAR=$(func) to capture.

Re: [gentoo-dev] [PATCH] app-portage/eclass-manpages: @DEFAULT_UNSET -> @DEFAULT-UNSET

On sob, 2017-04-29 at 14:05 -0400, Davide Pesavento wrote: > On Sat, Apr 29, 2017 at 1:40 PM, Michał Górny wrote: > > Dnia 29 kwietnia 2017 19:23:49 CEST, Davide Pesavento > > napisał(a): > > > On Sat, Apr 29, 2017 at 1:57 AM, Michał Górny

Re: [gentoo-dev] [PATCH] app-portage/eclass-manpages: @DEFAULT_UNSET -> @DEFAULT-UNSET

On nie, 2017-04-30 at 06:03 +1200, Kent Fredric wrote: > On Fri, 28 Apr 2017 16:39:45 +0200 > Michał Górny wrote: > > > Change the unset value tag to '@DEFAULT-UNSET' to ensure consistent > > use of hyphen/underscore throughout eclassdoc. Before, one tag > > (@ECLASS-VARIABLE)

[gentoo-dev] [PATCH 3/4] www-client/chromium: Use eninja from ninja-utils

--- www-client/chromium/chromium-59.0.3067.0.ebuild | 19 +-- 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/www-client/chromium/chromium-59.0.3067.0.ebuild b/www-client/chromium/chromium-59.0.3067.0.ebuild index fb975c22b0cd..ac00f473bf45 100644 ---

[gentoo-dev] [PATCH 4/4] sys-apps/systemd: Use eninja from ninja-utils

--- sys-apps/systemd/systemd-.ebuild | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/sys-apps/systemd/systemd-.ebuild b/sys-apps/systemd/systemd-.ebuild index 7ff69d75cc9a..b4e1f943a599 100644 --- a/sys-apps/systemd/systemd-.ebuild +++

[gentoo-dev] [PATCH 2/4] cmake-utils.eclass: Use eninja from ninja-utils

--- eclass/cmake-utils.eclass | 52 +++ 1 file changed, 3 insertions(+), 49 deletions(-) diff --git a/eclass/cmake-utils.eclass b/eclass/cmake-utils.eclass index 07f719a62a8c..2b3c8d933d1a 100644 --- a/eclass/cmake-utils.eclass +++

[gentoo-dev] [PATCH 1/4] ninja-utils.eclass: Add a new eclass to handle calling ninja

--- eclass/ninja-utils.eclass | 57 +++ 1 file changed, 57 insertions(+) create mode 100644 eclass/ninja-utils.eclass diff --git a/eclass/ninja-utils.eclass b/eclass/ninja-utils.eclass new file mode 100644 index ..69216176ba61 ---

[gentoo-dev] [PATCH 3/3] app-portage/eix: Convert to tmpfiles.eclass (example)

Replace the use of systemd.eclass with more generic tmpfiles.eclass to install the tmpfiles.d file. Use tmpfiles_process to ensure that the directory is created and correctly owned instead of keepdir-ing it (which triggers QA warnings from Portage) and chown-ing it in pkg_postinst() (which is a

[gentoo-dev] [PATCH 2/3] tmpfiles.eclass: Explicit warn on ROOT != / to avoid breakage

--- eclass/tmpfiles.eclass | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/eclass/tmpfiles.eclass b/eclass/tmpfiles.eclass index 9cf040de987f..018ea45d4182 100644 --- a/eclass/tmpfiles.eclass +++ b/eclass/tmpfiles.eclass @@ -110,7 +110,18 @@ tmpfiles_process() {

[gentoo-dev] [PATCH 1/3] tmpfiles.eclass: Support using on non-Linux systems

Fix the eclass code to remove the misguided Linux conditionals. The whole purpose of the eclass was to avoid having to implement fallback logic for systems not having service manager tmpfiles.d support. Making it conditional to Linux implied that for non-Linux systems (Prefix, FreeBSD) we would

Re: [gentoo-dev] USE flag name collision in use.local.desc "graphite"

On Sun, 30 Apr 2017 09:48:58 -0400 Brian Evans wrote: > If they want to enable a flag to apply system-wide, then it does not > matter where the description is. To users, a USE flag is a USE flag. Terminology wise, this is more a side effect that users are exposed to global

Re: [gentoo-dev] USE flag name collision in use.local.desc "graphite"

On 04/30/2017 06:36 AM, Mart Raudsepp wrote: > Ühel kenal päeval, L, 29.04.2017 kell 22:32, kirjutas Walter Dnes: >> Is it considered a reportable bug? >> >> [i660][waltdnes][~] grep :graphite /usr/portage/profiles/*.desc >> /usr/portage/profiles/use.local.desc:dev-lang/gnat-gpl:graphite - Add

Re: [gentoo-dev] USE flag name collision in use.local.desc "graphite"

Ühel kenal päeval, L, 29.04.2017 kell 22:32, kirjutas Walter Dnes: >   Is it considered a reportable bug? > > [i660][waltdnes][~] grep :graphite /usr/portage/profiles/*.desc > /usr/portage/profiles/use.local.desc:dev-lang/gnat-gpl:graphite - Add > support for the framework for loop optimizations

[gentoo-dev] Bugzilla package list editing

Hello, I would like to point out that the package list is under the responsibility of the maintainers whose packages are getting stabilized, and therefore at least after the point architectures are CC'ed by maintainer, this field is completely off limits for any non- maintainer edits whatsoever.