Skip to content
Snippets Groups Projects
Commit 4ffb3869 authored by Jean-Paul Calderone's avatar Jean-Paul Calderone
Browse files

point out that niv's `tahoe-lafs` controls packaging

parent 2346b673
No related branches found
No related tags found
1 merge request!285Also test against Tahoe-LAFS master on CI
Hide whitespace changes
Inline Side-by-side
Showing
with 6 additions and 1 deletion
CONTRIBUTING.rst
+ 6
− 1
View file @ 4ffb3869
...@@ -50,13 +50,18 @@ To update to the current master@HEAD revision, run: ...@@ -50,13 +50,18 @@ To update to the current master@HEAD revision, run:
nix-shell --run 'niv update tahoe-lafs-master --branch master' nix-shell --run 'niv update tahoe-lafs-master --branch master'
It is also possible to pass ``pull/<pr-number>/head`` to test against a specific PR. It is also possible to pass ``pull/<pr-number>/head`` to test against a specific PR.
When feasible we also test against a released version of Tahoe-LAFS.
The Nix package depends on a version of Tahoe-LAFS determined by the "tahoe-lafs" niv entry.
When feasible this is a released version of Tahoe-LAFS.
To update to a new release, run: To update to a new release, run:
.. code:: shell .. code:: shell
nix-shell --run 'niv update --rev tahoe-lafs-A.B.C tahoe-lafs' nix-shell --run 'niv update --rev tahoe-lafs-A.B.C tahoe-lafs'
When it is not feasible to use a released version of Tahoe-LAFS,
niv's ``--branch`` or ``--rev`` features can be used to update this dependency.
.. note:: .. note::
Since tahoe-lafs doesn't have correct version information when installed from a github archive, Since tahoe-lafs doesn't have correct version information when installed from a github archive,
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment