From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repoman: check for deprecated eclasses
Date: Fri, 01 Sep 2006 11:05:15 -0400 [thread overview]
Message-ID: <44F84C2B.8020206@gentoo.org> (raw)
In-Reply-To: <ed975m$g28$1@sea.gmane.org>
Stefan Schweizer wrote:
> Hi,
>
> Repoman needs to check for deprecated eclasses, see
> http://bugs.gentoo.org/141677
>
> As a result of the discussion in the bug, we would like to add
> $PORTDIR/qa-data/eclass.deprecated
> to allow to deprecate eclasses properly and make repoman fail.
>
> This will allow us to avoid problems with new ebuilds for deprecated
> eclasses which result in bugs like
> Bug 141629 dev-util/systemtap-20060325.ebuild uses deprecated
> kernel-mod.eclass
> I believe the developer has not known anything about that kernel-mod is
> deprecated when making that ebuild. Now he ignores the bug and we have that
> old eclass used again :(
>
> Best regards,
> - Stefan
>
I would prefer to see a patch for this first, and then modify gentoo-x86
second; but I agree in principle. What of the conversation about 2
files, one for "this eclass is currently being deprecated" -> repoman
warning; and "this eclass is no longer usable" -> repoman failure.
Also the deprecated -> new-eclass mapping. Afaik that didn't go so well
for me; but I still like it ;)
old new
----- ------
foo.eclass new-foo.eclass
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-01 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 11:56 [gentoo-dev] repoman: check for deprecated eclasses Stefan Schweizer
2006-09-01 15:05 ` Alec Warner [this message]
2006-09-01 16:57 ` Danny van Dyk
2006-09-01 17:37 ` Brian Harring
2006-09-01 23:37 ` Danny van Dyk
2006-09-02 3:51 ` Brian Harring
2006-09-02 4:54 ` Daniel Ostrow
2006-09-02 5:57 ` Brian Harring
2006-09-01 15:39 ` Carsten Lohrke
2006-09-01 16:47 ` [gentoo-dev] " Stefan Schweizer
2006-09-01 16:47 ` [gentoo-dev] " Alec Warner
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=44F84C2B.8020206@gentoo.org \
--to=antarus@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