Created attachment 386174 [details] sphinx-intl-0.9.5.ebuild Description: Sphinx utility that make it easy to translate and to apply translation. sphinx-intl is a utility tool that provides several features that make it easy to translate and to apply translation to Sphinx generated document.
Comment on attachment 386174 [details] sphinx-intl-0.9.5.ebuild ># This file is generated by /usr/bin/pypi2portage automatically. That shouldn't be in there. The usual header is missing, too. >MY_PF=sphinx-intl-0.9.5.tar.gz >MY_PD=sphinx-intl-0.9.5 That looks wrong. >DESCRIPTION="Sphinx utility that make it easy to translate and to apply translation." The spelling should be corrected here. make -> makes translation -> translations >HOMEPAGE="https://bitbucket.org/shimizukawa/sphinx-intl" >#SRC_URI="http://what/${MY_PF}" What does this comment do? >SRC_URI="https://pypi.python.org/packages/source/s/sphinx-intl/sphinx-intl-0.9.5.tar.gz" sphinx-intl -> ${PN} sphinx-intl-0.9.5 -> ${P} >KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86" Did you really test on all those architectures? >src_unpack() { > distutils_src_unpack > > if [ -f fixsetup.py ]; then > einfo 'Run fixsetup.py' > ${python} fixsetup.py > fi Looks like everything after distutils_src_unpack should go into src_prepare().
inherit distutils Oh dear. # This file is generated by /usr/bin/pypi2portage automatically. suggests this ebuild was generated by an ebuild generator that I have thus far refused to even look at. HINT; Ebuild generated with pypi2pkgsys This ebuild is merely proof of why. It starts with inheriting the now defunct 'old' (planned to eventually be deprecated) eclass. From there it was all down hill. rej's critique is correct but it's only a start. The substitute for >SRC_URI="https://pypi.python.org/packages/source/s/sphinx-intl/sphinx-intl-0.9.5.tar.gz" by rej although correct has another commonly used alternative present in dozens of pythonic ebuilds. The adjustments are just too numerous to even contemplate to begin illustrating here. I suggest you join the irc channel for python and I'm content to go thru this. However, step one is to make a case for why it need be added. IF it's a new dep for a package already present, THEN no problemo. Otherwise there is a problemo. I could just re-write it, but you'd be none the wiser.
Created attachment 427010 [details] sphinx-intl-0.9.9.ebuild I created a very simple ebuild for the sphinx-intl-0.9.9, but it does not work for some reason. When I try to emerge it, I get the following error: =============== error: Error: setup script specifies an absolute path: /var/tmp/portage/dev-python/sphinx-intl-0.9.9/work/sphinx-intl-0.9.9-python2_7/sphinx_intl.egg-info/PKG-INFO setup() arguments must *always* be /-separated paths relative to the setup.py directory, *never* absolute paths. =============== If I download the source archive, unpack it and run python2.7 setup.py build everything works fine, and does not rise the error mentioned above. I tried to search the solution over the Internet, but the only related question I found is this one: http://stackoverflow.com/questions/18085571/pip-install-error-setup-script-specifies-an-absolute-path However, it does not make it clear what to do in order to solve the issue. Therefore I decided to upload my current ebuild and ask for your opinions. Maybe you are familiar with this problem. Thanks!
Created attachment 543212 [details] sphinx-intl-0.9.11.ebuild sphinx-intl-0.9.11 seems to work OK (attached with some updates).
Created attachment 543214 [details] sphinx-intl-0.9.11.ebuild
