Yes, that's what I meant. You want to point to archives, because they don't change; tarballs will be regenerated on the fly by github, so they do not have fixed checksums and you would have to either make "fake" accesses to them every so often so github thinks they are still in use and won't remove and regenerate them, or update the checksums every week or so for the latest generated tarball. Neither one is worth the effort.
On Fri, Apr 15, 2016 at 8:50 PM, Abdulrahman Alshammari <[email protected] > wrote: > This is what is actually said; > "Since the github portgroup uses "tarball" downloads, not "archive" > downloads, this also means the checksums will change. " > > > --------------------------------------------------------------------------------------------------------------- > > Note: It might appear my name as "Ziad Ali" instaed of "Abdulrahman > Alshammari". > This is an issue that I am trying to fix. > > On Apr 15, 2016, at 8:39 PM, Brandon Allbery <[email protected]> wrote: > > On Thu, Apr 14, 2016 at 11:24 PM, Abdulrahman Alshammari < > [email protected]> wrote: > >> I was asked to change some parts of portfile. I did that except the >> checksums. I was told that the checksums will be changed because the github >> port. Can someone let me know how I can change it since using the same way >> will always generate the same checksums? If there any further changed, >> please let me know. > > > That sounds a bit confused. My guess is they asked you to use a release > tarball, because github generates non-release tarballs on the fly and > removes them if they haven't been accessed in a while, so the checksums are > not stable. (Release tarballs do have stable checksums.) > > -- > brandon s allbery kf8nh sine nomine > associates > [email protected] > [email protected] > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > > > -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
