Am 05.06.2010 16:43, schrieb Arfrever Frehtes Taifersar Arahesis: > 2010-05-27 16:33:39 Thomas Sachau napisaƂ(a): >> Hi together, >> >> since i am not able to get any real argument or even discussion on IRC nor on this mailing list from >> Arfrever (main person behind those changes), i would like to raise the following points now on this >> mailing list as told on IRC, so he gets the chance to answer those points and to clear the issues: >> >> -major changes to python eclasses have been done without peer review on this mailing list. > > There weren't any major changes in python.eclass in last months. In r1.96:r1.100 I committed a set of minor changes. > Some code was moved, which might cause false impression that there were some major changes: > - "MISCELLANEOUS FUNCTIONS" section (with 8 functions) was moved to before "FUNCTIONS FOR PACKAGES SUPPORTING > INSTALLATION FOR MULTIPLE PYTHON ABIS" section. > - python_pkg_setup() function was moved to "MISCELLANEOUS FUNCTIONS" section. > - A part of python_mod_cleanup() function was split to _python_clean_compiled_modules() function. > python_mod_cleanup() now calls _python_clean_compiled_modules(). > - 2 loops in python_mod_optimize() were divided and some code was reindented. You dont call the support for multiple python slots a "major change"? I did not see any RFC about your idea, concept or implementation. Even when other people, after the implementation was done, tried to talk with you about your way and pointing out other possible ways, which would be less complex (e.g. the "ruby way" or implementation on package manager side), you did not listen or refused to accept them because some optional additional feature might not work with that way. > >> This includes pulling in python-3* versions > > It's untruth. python.eclass or distutils.eclass don't enforce any particular version of Python. If any package does inherit python or distutils eclass, then those eclasses do pull in "dev-lang/python", which is unversioned, so it will always pull in the latest version, in this case python-3*. You could change this, so it allows any major installed slot to satisfy the python dependency. Additionally, your implementation pulls in python-3* for packages, which support multiple versions of python, but would work fine with the already installed python-2* version. This behaviour might be fine, when one could actually use python-3* as main version, but currently you pull in an unneeded and unused python slot. And your current implementation requires the use of another tool, python-updater, to maintain python related ebuilds, since your current implementation does not allow the package manager to see the needed/used dependencies and to (re)compile the packages as needed. > >> -A news item, which is only shown, once python-3* is installed. >> >> It is only shown _after_ installation of python-3. > > You might file an enhancement request for Portage to show news items before installation. Huh? Your news item explicitly requires the installation of python-3, before it is shown. This has nothing to do with the package manager, it is, what you define in your news item. > >> Beside those points, one additional main issue is, that i and others dont seem to be able to have a >> discussion with Arfrever about this topics. > > I'm answering to new (unanswered), rational arguments about these topics. > >> He says, he has no time for it or says, that he already had shown arguments, but cannot show >> any evidence or just stops responding without any note. > > There had been multiple threads about Python 3. Read e-mails written by me or Dirkjan Ochtman in the following threads: > http://archives.gentoo.org/gentoo-dev/msg_115ce6fa1a09de286bf58db12df463c6.xml > http://archives.gentoo.org/gentoo-dev/msg_814e67764c17f88bde94f22e9a392e4f.xml > http://archives.gentoo.org/gentoo-dev/msg_2591c1b9a7e7b72383d3841bc05dc417.xml I did read the threads about python-3, but i still dont see any real argument, why you want everyone to install python-3*, also it is not required, not needed and not used. Also, you have written, that the python team does not suggest to mask python-3, but did not give any reason for that. So could you do that now? -- Thomas Sachau Gentoo Linux Developer