public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Deprecation of python_version(), 	python_mod_exists(), python_tkinter_exists(), distutils_python_version() and  distutils_python_tkinter() in EAPI <=2
Date: Wed, 03 Mar 2010 17:55:41 +0200	[thread overview]
Message-ID: <4B8E867D.4060908@gentoo.org> (raw)
In-Reply-To: <20100303064011.08bd999d@gentoo.org>

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

On 03/03/2010 02:40 PM, Ryan Hill wrote:
> On Wed, 03 Mar 2010 13:09:49 +0200
> Petteri Räty <betelgeuse@gentoo.org> wrote:
> 
>> On 3.3.2010 11.23, Nirbheek Chauhan wrote:
>>> 2010/3/3 Tomáš Chvátal <scarabeus@gentoo.org>:
>>>>>> Removing eclass functions like this is not allowed by current policy. If
>>>>>> you want to do it, you should discuss about changing policy.
>>>>>
>>>>> ?!
>>>>>
>>>>> since when?
>>>>>
>>>> Since ever.
>>>> If you change eclass abi you need to rename it.
>>>>
>>>
>>> I think you can *add* functions and variables to eclasses, you can
>>> change *how* a function works internally, you can *fix* problems with
>>> functions (which would technically result in a change in API). I don't
>>> think it has ever been as strict as, say, the kernel ABI interface.
>>>
>>
>> Yes, eclasses go along the same lines as shared libraries, which is
>> probably what Tomáš meant any way.
> 
> Is this actually documented anywhere?  Or is this another of our
> "this-is-policy-because-everyone-knows-it's-policy" policies?  I know there
> was a technical issue with removing pkg_*_rm functions way-back-when, but if
> there's no technical reason why functions can't be deprecated, and we're just
> clinging to policy in the name of policy, then I can't say I see the point.
> 

Big eclass changes should go through gentoo-dev so someone here will
point it out at least. Devmanual should document it so I challenge
anyone to submit a patch:

http://devmanual.gentoo.org/eclass-writing/index.html
git+ssh://git.gentoo.org/var/gitroot/devmanual.git

Also policies should be changed when they don't make sense any more as I
said in my first response but I am not sure if that's the case here.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2010-03-03 15:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 18:27 [gentoo-dev] Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2 Arfrever Frehtes Taifersar Arahesis
2010-03-03  6:52 ` Petteri Räty
2010-03-03  7:52   ` [gentoo-dev] " Ryan Hill
2010-03-03  8:47     ` Tomáš Chvátal
2010-03-03  9:23       ` Nirbheek Chauhan
2010-03-03 11:09         ` Petteri Räty
2010-03-03 12:40           ` Ryan Hill
2010-03-03 15:55             ` Petteri Räty [this message]
2010-03-03 21:39               ` Ryan Hill
2010-03-04  7:13                 ` Petteri Räty
2010-03-04  7:39                   ` Ulrich Mueller
2010-03-04  7:55                     ` Petteri Räty
2010-03-04  9:43                       ` Ulrich Mueller
2010-03-05  3:19                         ` Ryan Hill
2010-03-03 12:47       ` Ciaran McCreesh
2010-03-03 15:08         ` Duncan
2010-03-03 15:46         ` Petteri Räty
2010-03-05  9:54           ` [gentoo-dev] " Peter Hjalmarsson
2010-03-05 11:12             ` Petteri Räty
2010-03-05 20:14               ` [gentoo-dev] " Ryan Hill
2010-03-05 21:00                 ` Mike Frysinger
2010-03-06  5:42                 ` Petteri Räty
2010-03-05 18:40             ` Duncan
2010-03-05 19:16       ` Mike Frysinger
2010-03-03 14:02   ` [gentoo-dev] " Jeremy Olexa

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=4B8E867D.4060908@gentoo.org \
    --to=betelgeuse@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