Developers' guide: Update "Packaging Third-Party Code" regarding upstream_url
Closed this issue · 13 comments
... and other features of sage --package.
https://doc.sagemath.org/html/en/developer/packaging.html
Sources:
- https://wiki.sagemath.org/ReleaseTours/sage-9.1#For_developers-1
- https://wiki.sagemath.org/ReleaseTours/sage-9.2#For_developers:_Upgrading_packages
CC: @seblabbe @tobiasdiez @jhpalmieri @dimpase @paulmasson
Component: documentation
Author: Matthias Koeppe
Branch/Commit: 86e048f
Reviewer: Sébastien Labbé
Issue created by migration from https://trac.sagemath.org/ticket/30895
Author: Matthias Koeppe
this is a bit off-topic:
Is there away to minimize checking of mirrors for tarballs that aren't there; if one adds an upstream_url, and starts installing this package, then it takes long time for Sage to discover that the tarball is not on mirrors, before using upstream_url.
Replying to @dimpase:
Is there away to minimize checking of mirrors for tarballs that aren't there; if one adds an upstream_url, and starts installing this package, then it takes long time for Sage to discover that the tarball is not on mirrors, before using upstream_url.
You can edit the file upstream/mirror_list.
Can you add after
+--enable-download-from-upstream-url``. Then Sage will fall back to
+downloading package tarballs from the ``upstream_url``. It is then no
+longer necessary to manually download upstream tarballs.
something like
One can manually trim `upstream/mirror_list` to fewer mirrors so that the fallback
happens quicker.
Branch pushed to git repo; I updated commit sha1. New commits:
86e048f | src/doc/en/developer/packaging.rst: Trimming mirror list |
bot is green for the doc changes.
Reviewer: Sébastien Labbé
Thanks!
Changed branch from u/mkoeppe/developers__guide__update__packaging_third_party_code__regarding_upstream_url to 86e048f