-
-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support downloading of symlinked tarballs #24476
Comments
New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:7
So whats the plan, have a symlinked tarball or two packages refer to the same tarball? The latter seems more sane to me. Whereas the former raises some questions, e.g. what to upload to mirrors. Looking up tarball name -> package name isn't really important I think. Could just return a set of matching packages. |
comment:8
Two packages referring to the same tarball. In #12426 I ended up creating a spkg for gfortran which of course uses gcc's tarball. |
comment:9
Replying to @vbraun:
It is needed because the tarballs on the server are stored per package. The URL is something like |
comment:12
looks good to me. |
Reviewer: Dima Pasechnik |
Changed branch from u/jdemeyer/support_downloading_of_symlinked_tarballs to |
#12426 introduces a new package "gfortran" which reuses the gcc tarball. This is done by symlinking various files in
build/pkgs/gfortran
tobuild/pkgs/gcc
. This confuses the tarball downloader, so we add support for such symlinks insage_bootstrap
.CC: @embray @vbraun @kiwifb
Component: build
Author: Jeroen Demeyer
Branch/Commit:
5b8e8dd
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/24476
The text was updated successfully, but these errors were encountered: