#16629: sage-fix-pkg-checksums munches build/pkgs/<packagename>/checksums
-------------------------------------+-------------------------------------
       Reporter:  charpent           |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  minor              |    Milestone:  sage-6.3
      Component:  build              |   Resolution:
       Keywords:                     |    Merged in:
        Authors:                     |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/charpent/sage_fix_pkg_checksums_munches_build_pkgs__packagename__checksums| 
 d941afd9150164e979b7df98b2e574cdacd78053
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by vbraun):

 Replying to [comment:14 rws]:
 > Minus the patchlevel, to be exact.

 Exactly, which is another reason for why the `package-version.txt` is the
 authorative version. Also, the Sage build process uses the `package-
 version.txt` timestamp to determine whether a package needs to be rebuilt,
 which is why you need to add the patch level here.

 The `sage-fix-pkg-checksum` iterates over upstream/ and then ignores any
 entries for which there is no corresponding `build/pkgs/*/package-
 version.txt`. So that it can auto-generate the entire checksums.ini
 (though it trips over cases). E.g. hashdist has a much more sensible
 system of caching upstream sources.

--
Ticket URL: <http://trac.sagemath.org/ticket/16629#comment:16>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to