Currently, the dependency graph shows different nodes for, e.g., "swh.core" and
"swh.core[db]". With this change the two nodes are merged together.

While it is interesting to know which precise part of a module others depend
on, that is not the purpose of the dependency graph, which is meant to give
only a high-level view of dependencies.

Addresses T1983

Related T1887

Archit Agrawal authored 5 years ago and Stefano Zacchiroli committed 5 years ago

Summary:
(T1696)
Fixed a typo in developer-setup. In the second line of the first point, it should be your modifications instead of yout modifications.

Reviewers: #reviewers, zack

Reviewed By: #reviewers, zack

Differential Revision: https://forge.softwareheritage.org/D1437

Matthew Vernon authored 5 years ago and Stefano Zacchiroli committed 5 years ago

Reviewers: #reviewers, zack

Reviewed By: #reviewers, zack

Subscribers: vlorentz, anlambert

Differential Revision: https://forge.softwareheritage.org/D1430

- remove the manual setup guide since we do not want to promote (and
  maintain) this approach any more,
- few rewordings in getting-started.rst iteself
- in the developer-setup guide:
  - rewordings
  - copy the 'install depencencies' from the manual-setup guide,
  - add the missing step bin/update
  - remove the docker setup part (been integrated in the swh-docker-dev's
    README)
  - add a section on unit tests

Thibault Allançon authored 6 years ago and Antoine Pietri committed 6 years ago

Reviewers: #reviewers, seirl

Reviewed By: #reviewers, seirl

Subscribers: seirl

Differential Revision: https://forge.softwareheritage.org/D1217

This is no longer true since 0bcfadec.

This is no longer true since 0bcfadec.

Improving the postactivate hook to work both for zsh/bash users

- a very basic docker-based quick start,
- a more advanced developer setup guide (using mixed docker/venv install),
- the original manual setup guide.

Closes T1341

Without this dependency, the pifpaf tests won't execute. They will
fail with a cryptic error.

That cryptic error message is currently fixed by pifpaf's author. It's
pending in a PR and should soon land.

Related P341
Related https://github.com/jd/pifpaf/issues/108
Related https://github.com/jd/pifpaf/pull/119

- do not silence sphinx CLI invocations (it's bad for logs)
- avoid $(apidoc_dep) variable (it doesn't exist for any other *-stamp)

Reviewers: #reviewers, ardumont

Reviewed By: #reviewers, ardumont

Differential Revision: https://forge.softwareheritage.org/D880

Depends on D834

This will allow the CI to run the building job with sphinx options like
`-W` (aka "turn warnings into errors").

- back to assets only building in each package
- run sphinx-autodoc on the whole swh package at once

we do not really need a local standalone buildable sphinx project in each swh
subpackage, so running a full 'make html' in each of them is not required any
more.

Since we want to build the doc at once instead of building each swh subpackage
independantly, we need to run apidoc on the whole swh package.

This is done by actually running the apidoc on the pip installed swh
packages instead of the source repositories, since sphinx-apidoc does
not seem to support multiple MODULE_PATH as cmdline argument.

So it's best to use tox to build the doc.

Related to T1330.

so that we can have some generic substitutions which can be used consistently
in the doc.