remove SUMO tarballs, rewrite "desert island" build instructions #2752
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2752
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that we're on pip, the Right Way to do a "desert island" build is to do a regular build before you get shipwrecked, then use pip's http/wheel cache on the island. We don't need separate tarballs for this.
I'd like to walk through our dependency tree and check that everything is available on pypi (as well as surveying which platforms have binary wheels available), but then I think we can stop hosting copies of our dependencies for the new release.
The actionable steps are:
tahoe-deps
tarballsetup.cfg
to remove thefind_links=
clause that points tomisc/dependencies
,tahoe-deps
, and../tahoe-deps
(leaving the ones that point at tahoe-lafs.org for now, see #2750)docs/desert-island.rst
with a description of pip's cache, its default behavior, pointers to the pip docs to control its behavior, and instructions on what to do before and after the shipwreck (or getting on an airplane, or other offline development environment)In 1fb7cc7/trunk:
In 4f98c1d/trunk:
In 17886c5/trunk:
I think that's all of it.