Created attachment 189679 [details]
Created attachment 189680 [details]
Created attachment 189681 [details]
If we use github to download releases, why not to switch to USE_GITHUB instead?
(In reply to Vsevolod Stakhov from comment #3)
Because there is the policy that if github has tarballs, they should be preferred, unless you want to use a specific GH_TAGNAME for some reason.
That's irrelevant to USE_GITHUB: you can use releases with this option as well, as there were certain problems in the past with loading of raw tarballs from github. From my point of view it is better to leave that for USE_GITHUB which should be able to use the best available method to get those tarballs.
(In reply to Vsevolod Stakhov from comment #5)
But does it really do that?
USE_GITHUB just downloads by the tagname, I think.
(In reply to Yuri Victorovich from comment #6)
For example, recently portmgr@ demanded that MASTER_SITES is kept in google-perftools instead if USE_GITHUB.
(In reply to Yuri Victorovich from comment #7)
portmgr@: Why did you not use the released tarball and switched to using a git archive? Unless there is a bug in the released tarball, it goes against our policy to always try and use the tarballs that project release.
(In reply to Yuri Victorovich from comment #8)
Sourceforge seems broken. A lot of this:
=> Attempting to fetch http://superb-dca2.dl.sourceforge.net/project/potassco/clasp/3.3.3/clasp-3.3.3-source.tar.gz
fetch: http://superb-dca2.dl.sourceforge.net/project/potassco/clasp/3.3.3/clasp-3.3.3-source.tar.gz: Not Found
=> Attempting to fetch http://superb-sea2.dl.sourceforge.net/project/potassco/clasp/3.3.3/clasp-3.3.3-source.tar.gz
fetch: http://superb-sea2.dl.sourceforge.net/project/potassco/clasp/3.3.3/clasp-3.3.3-source.tar.gz: Not Found
Same for many other projects.
I will update using USE_GITHUB.