It seems net-misc/dropbox runs with a bundled version of python. Is this intended? If so, why is there a python_single_target_X in the ebuild? Specifically, I noted that even when python_single_target_3X is specified, dropbox will start by default with python27. Furthermore adapting PYTHON_COMPAT in the ebuild to python_single_target_36 and starting /opt/dropbox/dropbox_py3 will run with a bundled version of python35. Currently the ebuild only supports python_targets_python2_7 and python_targets_python3_5, meaning that it can't be installed on systems with PYTHON_SINGLE_TARGET="python3_6". Due to above considerations, what about adding `python3_6` to PYTHON_COMPAT or removing the python variables completely from the ebuild as long as they are anyways ignored (?). Thanks!
(In reply to Leonard Lausen from comment #0) > It seems net-misc/dropbox runs with a bundled version of python. Is this > intended? If so, why is there a python_single_target_X in the ebuild? not bundled per-se. dropbox is written in python and then precompiled to a binary. > Specifically, I noted that even when python_single_target_3X is specified, > dropbox will start by default with python27. Furthermore adapting > PYTHON_COMPAT in the ebuild to python_single_target_36 and starting > /opt/dropbox/dropbox_py3 will run with a bundled version of python35. > > Currently the ebuild only supports python_targets_python2_7 and > python_targets_python3_5, meaning that it can't be installed on systems with > PYTHON_SINGLE_TARGET="python3_6". The python stuff was originally there so the deps would be pulled in properly. the deps have been getting weirder over the last few releases so ive had to use the bundled ones instead of unbundling. not being able to install on a python3_6 system sounds problematic tho. i guess i'll see if dropping all the deps is possible otherwise i'll just put it back to 2_7 like it was before.
Thanks for the explanation! Just for clarification, I believe if you specify `PYTHON_COMPAT=( python2_7 python3_5 python3_6 )` in the ebuild it will work on python27, python35 and python36 systems. If you only specify python2_7 it won't work on pure python3 systems. So specifying all 3 (or even more) seems preferable to just specifying python2_7.
This should be fixed now, i added python3_6 to the lastest bump, so it should have all the types so you can pick whichever works. please re-open or make a new bug if there are still issues
