[103586] trunk/dports/python/py-xlrd/Portfile

Ryan Schmidt ryandesign at macports.org
Sat Mar 2 09:40:04 PST 2013


On Mar 2, 2013, at 11:37, Jeremy Lavergne wrote:

>> Why were these master_sites and distname lines necessary? With the github portgroup you shouldn't need to add those; the defaults should work. If I remove these lines, the checksums then differ, but the contents of the files are the same.
> 
> It's the same as the github.master_sites except that it uses the "archive" from the site, rather than "tarball". I went with this because that's the link on the site, which shouldn't be recreated dynamically...
> 
> Do we know which is not the dynamic one?

I think this "archive" thing is part of the new layout they rolled out a few months ago:

https://trac.macports.org/ticket/36862

I did not investigate switching to this layout because the old way seemed to still work, and this would mean changing every port since checksums change.

I have no idea what the github servers do behind the servers w.r.t. dynamically generating tarballs or not.




More information about the macports-dev mailing list