From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Versioning of eclasses and possibly functions inside ebuilds
Date: Wed, 28 Dec 2011 11:21:08 -0800 [thread overview]
Message-ID: <4EFB6C24.1070307@gentoo.org> (raw)
In-Reply-To: <CAD6zcDzTL2LeEwe-DRyH7b=UqBm+7TJ1xMgz_Nb0zQiuzkuNnQ@mail.gmail.com>
On 12/28/2011 05:12 AM, Francesco Riosa wrote:
> Seem to me that append a time slice to the function, in the name or as
> a parent function that call the underling function can solve most of
> the versioning/deprecation problems
I've overheard Arfrever discussing a similar approach in funtoo's irc
channel, where the ebuild would set a variable prior to inherit if it
wants to use a specific eclass API. For the python eclass, he's planning
to have ebuilds set the PYTHON_ECLASS_API variable to use the new API.
When the variable is unset, the eclass will default to the older API.
--
Thanks,
Zac
next prev parent reply other threads:[~2011-12-28 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 13:12 [gentoo-dev] Versioning of eclasses and possibly functions inside ebuilds Francesco Riosa
2011-12-28 19:01 ` Zac Medico
2011-12-29 2:28 ` Francesco Riosa
2011-12-28 19:21 ` Zac Medico [this message]
2011-12-29 2:37 ` Francesco Riosa
2011-12-29 3:36 ` Brian Harring
2011-12-29 10:49 ` Francesco Riosa
2011-12-29 15:28 ` Jeroen Roovers
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=4EFB6C24.1070307@gentoo.org \
--to=zmedico@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