The build instructions do not specify the list of dependencies

[sel]

​https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst

says to write to the list in case of trouble.

[zooko]

I don't want quickstart.rst to contain a list of dependencies, because that would make it longer and more complicated, and because a user who is following quickstart.rst doesn't need to know what the dependencies are, since they get downloaded automatically.

Clarifications:

• sel had a problem with missing dependencies (see #2063), but sel was not following quickstart.rst at that time, because sel was invoking python setup.py install, which quickstart.rst does not instruct you to do.
• There is a list of dependencies, in src/allmydata/_auto_deps.py.
• There is probably also more information on wiki:AdvancedInstall, but I wouldn't know, because I don't look at that page.

[sel]

Replying to zooko:

I don't want quickstart.rst to contain a list of dependencies, because that would make it longer and more complicated, and because a user who is following quickstart.rst doesn't need to know what the dependencies are, since they get downloaded automatically.

in my case they didn't.

Clarifications:

• sel had a problem with missing dependencies (see #2063), but sel was not following quickstart.rst at that time, because sel was invoking python setup.py install, which quickstart.rst does not instruct you to do.

Apparently I am not the first one to encounter this problem. See #1494.

• There is a list of dependencies, in src/allmydata/_auto_deps.py.

it is well hidden from the eyes of a 'first time user'.

• There is probably also more information on wiki:AdvancedInstall, but I wouldn't know, because I don't look at that page.

[zooko]

Hi Sel: thank you for the bug report! As far as I can tell, the remaining issues are tracked by #1494, #2063 (and perhaps others), so it makes sense to leave this ticket closed.

[daira]

Replying to sel:

Replying to zooko:

I don't want quickstart.rst to contain a list of dependencies, because that would make it longer and more complicated, and because a user who is following quickstart.rst doesn't need to know what the dependencies are, since they get downloaded automatically.

in my case they didn't.

In fact they do when following the quickstart.rst instructions (which specify to use python setup.py build, not python setup.py install).

[sel]

I think you don't understand: I used both in sequence, so if the build had downloaded all dependencies, I should not have any problems during the install. But this wasn't the case.

[zooko]

Replying to sel:

I think you don't understand: I used both in sequence, so if the build had downloaded all dependencies, I should not have any problems during the install. But this wasn't the case.

sel, as far as I understand, when you ran python setup.py build, it did download all of the dependencies (and installed them into a subdirectory of your source tree named "support/"), and then when you ran python setup.py install, it did not install them into your system directories. The fact that it doesn't install dependencies into your system directories when you run python setup.py install is the subject of ticket #1494.

[sel]

Replying to zooko:

Replying to sel:

I think you don't understand: I used both in sequence, so if the build had downloaded all dependencies, I should not have any problems during the install. But this wasn't the case.

sel, as far as I understand, when you ran python setup.py build, it did download all of the dependencies (and installed them into a subdirectory of your source tree named "support/"), and then when you ran python setup.py install, it did not install them into your system directories. The fact that it doesn't install dependencies into your system directories when you run python setup.py install is the subject of ticket #1494.

Thanks. I should have written 'installed' instead of 'downloaded'.