"upstream" tarballs management

[Jean-Pierre Flori]

Dear all,

Who or what is in charge of the upstream directory, as it is not git tracked?
I've made a quick search here but nothing seemed definitive.

Is it automatically fed when packages are upgraded?
It doesn't seem every spkg has a spkg-src script so it is doubtful.

And as long as we have mercurial betas for 5.13, are the src dir automatically tar'ed and upped when the betas are merged into the git repo?

The question recently came up for an upgrade to R which does not appear in the upstream dir, see #14706.

Best,
JP

[Volker Braun]

Afaik there is no particular system in place, just as with the old spkgs. The web site maintainer has to copy the package to the web server directory. IMHO we should have a group (gid) and g+w directory on boxen such that core sage developers can add tarballs before tickets are merged. After the git version the buildbot will of course notice any missing tarballs before release.

[Robert Bradshaw]

In git we do record the expected hash of the tarball so at the very
least you can't get the wrong one without one knowing.

> --
> You received this message because you are subscribed to the Google Groups
> "sage-git" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-git+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.