Archives
Archives
| From: | Nirbheek Chauhan <nirbheek@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| 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 09:24:02 | ||
| Message-Id: | 8b4c83ad1003030123j171325a7o105b7887d40c0303@mail.gmail.com | ||
| In Reply to: | Re: [gentoo-dev] Re: Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2 by "Tomáš Chvátal" |
||
| 1 | 2010/3/3 Tomáš Chvátal <scarabeus@g.o>: |
| 2 | >>> Removing eclass functions like this is not allowed by current policy. If |
| 3 | >>> you want to do it, you should discuss about changing policy. |
| 4 | >> |
| 5 | >> ?! |
| 6 | >> |
| 7 | >> since when? |
| 8 | >> |
| 9 | > Since ever. |
| 10 | > If you change eclass abi you need to rename it. |
| 11 | > |
| 12 | |
| 13 | I think you can *add* functions and variables to eclasses, you can |
| 14 | change *how* a function works internally, you can *fix* problems with |
| 15 | functions (which would technically result in a change in API). I don't |
| 16 | think it has ever been as strict as, say, the kernel ABI interface. |
| 17 | |
| 18 | -- |
| 19 | ~Nirbheek Chauhan |
| 20 | |
| 21 | Gentoo GNOME+Mozilla Team |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] Re: Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2 | "Petteri Räty" <betelgeuse@g.o> |