public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Klima <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Deprecating an eclass
Date: Mon, 18 Feb 2008 17:19:55 -0500	[thread overview]
Message-ID: <47BA048B.1020602@gentoo.org> (raw)
In-Reply-To: <20080218204951.337fe426@snowcone>

Ciaran McCreesh wrote:
> On Mon, 18 Feb 2008 15:43:56 -0500
> Doug Klima <cardoe@gentoo.org> wrote:
>   
>> Ok. I guess no one else has any feelings about this.
>>
>> Potentially doing something like:
>>
>> DEPRECIATED="$DEPRECATED $ECLASS"
>>     
>
> Deprecated != depreciated.
>   
You caught my typo. You clearly still got the meaning of the e-mail...
>   
>> at the top of each deprecated eclass. In the end $DEPRECATED would
>> have a list of all the eclasses that are deprecated?
>>
>> Maybe even:
>>
>> DEPRECATED_MYECLASS="myreplacement"
>>
>> would mean that myeclass.eclass is replaced by myreplacement.eclass ?
>>     
>
> Well, that depends upon whether you want it to be part of the C/P-V
> metadata... If you do, it's a cache format change (and you can't easily
> do DEPRECATED_*). But then, deprecation is a property of the eclass,
> not an C/P-V.
>
>   
Deprecation is a property of the eclass. Not of an ebuild. The point is 
to allow utilities and users/developers to clearly see that an eclass is 
deprecated and what they should be using in place of it.
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-18 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 22:18 [gentoo-dev] [RFC] Deprecating an eclass Doug Klima
2008-02-18 20:43 ` Doug Klima
2008-02-18 20:49   ` Ciaran McCreesh
2008-02-18 22:19     ` Doug Klima [this message]
2008-02-18 22:25       ` Ciaran McCreesh
2008-02-19  1:08         ` Petteri Räty
2008-02-18 23:20   ` Torsten Rehn

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=47BA048B.1020602@gentoo.org \
    --to=cardoe@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