- If this package can be used as a library and installs Python modules (*.so or *.py) into directories specific to given versions of Python, then consider supporting installation for multiple Python versions. Please read section "Types of packages" in documentation [1]. - Ensure that the ebuilds do not use deprecated functions or variables. - Please check if Python 3 is supported by this package. You can temporarily set Python 3 as main active version of Python to properly test if this package supports Python 3. - If this package does not support Python 3: - Specify dependency on Python 2. You can use PYTHON_DEPEND helper variable, which should be set before inheriting of python eclass. - If this package cannot support installation for multiple versions of Python, then set active version of Python using python_set_active_version(). - Ensure that shebangs in installed scripts specify correct version of Python. If shebangs are too generic (e.g. '#!/usr/bin/python'), then you can use python_convert_shebangs() to convert shebangs. (Wrapper scripts generated by python_generate_wrapper_scripts() do not require any changes.) - To ensure that changes applied to the ebuilds are sufficient, please temporarily set Python 3 as main active version of Python and test if this package can be properly installed and if it works at run time. Please see documentation [1] for more details. [1] http://www.gentoo.org/proj/en/Python/developersguide.xml
Homepage is dead, last updated 2005, all it is is a python script.
reopened I think I closed this in error.
# Jeremy Olexa <darkside@gentoo.org> (12 Jun 2010) # Dead upstream, last update from 2005, no maintainer. # Removed in 60 days by treecleaners, bug 311533 app-misc/mved
I use this program all of the time, and would like for it to remain in portage. What do I need to do in order to ensure this happens?
(In reply to comment #4) You should create a patch for the ebuild and convince a developer to commit this patch.
Created attachment 239523 [details, diff] fixes syntax errors and runtime errors when using python-3 the shebang is #!/usr/bin/env python. I'm assuming that is fine to use. I've tested it with both 2 and 3, and both seem to work just fine. Since I've never ported anything from python-2 to python-3 before, so I may have done things in a non-optimal way.
(In reply to comment #6) I would suggest to firstly modify mved-1.2.ebuild, so that it uses Python 2, and next send patch for Python-3 compatibility to upstream and convince upstream to release new version.
Created attachment 240273 [details, diff] changes the ebuild to use python-2
To ask the upstream maintainer, should I just email the person in the README file? the project page at http://guerila.com seems to not exist (and has not existed since i started using mved in 2006 or so) If all else fails, I can host the files myself.
Is anything happening with this? it looks like mved is still masked and marked for deletion (also, it has been more than 60 days since Jun. 12).
Removed from cvs. Please if you are interested to have this software in main tree open a bug report where it has proper webpage bugtracker and repository. Or you can try to get your ebuild included in sunrise overlay. Cheers
