public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: mgorny@gentoo.org
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] repoman: Finally deprecate base.eclass
Date: Thu, 22 Oct 2015 22:03:05 +0100	[thread overview]
Message-ID: <20151022220305.70d1ba89@sf> (raw)
In-Reply-To: <1444548200-3454-1-git-send-email-mgorny@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

On Sun, 11 Oct 2015 09:23:20 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> Contributors are repeatedly adding base.eclass uses, so we should
> finally make the deprecation formal, even at the cost of adding warnings
> for some frequently used eclasses.
> 
> Signed-off-by: Michał Górny <mgorny@gentoo.org>
> ---
>  pym/repoman/checks/ebuilds/checks.py | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/pym/repoman/checks/ebuilds/checks.py b/pym/repoman/checks/ebuilds/checks.py
> index ae6d96e..a00d518 100644
> --- a/pym/repoman/checks/ebuilds/checks.py
> +++ b/pym/repoman/checks/ebuilds/checks.py
> @@ -409,6 +409,7 @@ class InheritDeprecated(LineCheck):
>  
>  	# deprecated eclass : new eclass (False if no new eclass)
>  	deprecated_eclasses = {
> +		"base": False,
>  		"bash-completion": "bash-completion-r1",
>  		"boost-utils": False,
>  		"distutils": "distutils-r1",
> -- 
> 2.6.1

I would also suggest:

- adding a @DEPRECATED documentation stanza
   right into base.eclass with a migration strategy link
- and a ewarn/eqawarn call to flag all offenders and prevent
   new ebuilds to creep dependency back

-- 

  Sergei

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2015-10-22 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  7:23 [gentoo-portage-dev] [PATCH] repoman: Finally deprecate base.eclass Michał Górny
2015-10-11 16:16 ` Alexander Berntsen
2015-10-11 16:45   ` Michał Górny
2015-10-11 16:51     ` Alexander Berntsen
2015-10-11 19:23       ` Zac Medico
2015-10-11 20:24         ` Zac Medico
2015-10-12 14:48           ` Michał Górny
2015-10-22 21:03 ` Sergei Trofimovich [this message]

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=20151022220305.70d1ba89@sf \
    --to=slyfox@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=mgorny@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