The tarballs are downloaded from sagemath.org (and, at some point in the future, our mirrors)
On Wednesday, April 2, 2014 5:55:54 PM UTC+1, kcrisman wrote: > > > > On Tuesday, April 1, 2014 3:24:36 PM UTC-4, John Cremona wrote: >> >> On 1 April 2014 19:01, kcrisman <kcri...@gmail.com> wrote: >> > >> > >> > On Tuesday, April 1, 2014 1:47:51 PM UTC-4, Volker Braun wrote: >> >> >> >> On Tuesday, April 1, 2014 6:32:24 PM UTC+1, Ralf Stephan wrote: >> >>> >> >>> So experimental packages are optional, not standard? >> >> >> >> The four categories are separate; a package is either experimental or >> >> optional or standard or huge (there are exactly 2 huge packages so its >> >> reasonably rare ;-) >> >> >> >> >> >>> What tickets should have component spkg-check? >> >> >> >> Tickets that are primarily focused on modifying spkg-check. >> >> >> >>> Where do optional packages live, after they are accepted? >> >> >> >> New-style optional packages are directories in build/pkgs/... just >> like >> >> standard ones. The only difference is that they are not build by >> default. >> >> >> > >> > So they no longer are downloaded from >> http://sagemath.org/packages/optional/ >> > ? (And their source is in Sage tarballs?) Or is that only true for >> > optional spkgs that have been migrated to the new format? >> >> In the new format there is no *.spkg file at all. The files in a >> subdirectory in build.pkg are just the install scripts + some other >> bits and pieces, all under git-revision control; the source code of >> the spkg is downloaded when first installed and thereafter lives in >> the upstream/ directory. When a new optional spkg is being reviewed >> the author of the ticket puts the new version (if there is a new >> upstream) onto some public machine where reviewers and release >> managers can find it. After acceptance that upstream tarball is put >> somewhere where the install script can find it (NOT any more in >> http://sagemath.org/packages/optional/ I think). >> >> For an example, look at build/pkgs/database_cremona_ellcurve, which >> contains 4 files: >> checksums.ini package-version.txt spkg-install SPKG.txt >> and also look at ticket #16013 where as well as a new git branch with >> tiny changes to those files you can find a link to the new upstream. >> > > > Right, but where does the optional (s)pkg live once merged? In Sage's > upstream/ directory as a tarball? *Always* downloaded from possibly flaky > non-canonicial, non-mirrored other sites? That's what I'm wondering. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
