- 🇺🇸United States smustgrave
Since there has been no follow up to #51 going to close out as outdated. If still a request please reopen addressing #51 comment and updating issue summary for D10 and up.
Thanks!
#11416: Please provide *.zip downloads. → would be a huge usability win for drupal.org. Dries even blogged about it. I've been working on the backend changes in project_release module to make this happen for a while. One of the last remaining hurdles to make it a reality is that update.module currently only knows about a single "Download" link from the XML and in the UI. We need to fix this. Ideally, in both D7 and D6, although it'd impact the string freeze in D6...
The relevant XML currently looks something like this:
<release_link>http://drupal.org/node/156281</release_link>
<download_link>http://ftp.drupal.org/files/projects/drupal-7.x-dev.tar.gz</download_link>
<date>1250813342</date>
<mdhash>6331b74cf71a09f699ff5a23d1207926</mdhash>
<filesize>1995307</filesize>
Update status itself doesn't even look at mdhash and filesize at this point. To prevent confusion with existing clients, I'd probably leave all of that in the XML, and just add some new stuff which newer clients would look at. Older clients will happily ignore the new data, and new clients will ignore the old. That seems easier than separate release history links to fetch some kind "schema-version-dependent" XML...
Anyway, I think the new XML should include something like this:
<release_link>http://drupal.org/node/156281</release_link>
<downloads>
<download>
<url>http://ftp.drupal.org/files/projects/drupal-7.x-dev.tar.gz</url>
<text>tar.gz</text>
<mdhash>6331b74cf71a09f699ff5a23d1207926</mdhash>
<filesize>1995307</filesize>
<filedate>1250813342</filedate>
</download>
<download>
<url>http://ftp.drupal.org/files/projects/drupal-7.x-dev.zip</url>
<text>zip</text>
<mdhash>6331b74cf71a09f699ff5a23d1209999</mdhash>
<filesize>1999666</filesize>
<filedate>1250813345</filedate>
</download>
</downloads>
Then, in the UI, instead of just Download as a link, We'd see:
It'll be a bit hard to implement/test this without real data on updates.d.o, and I'm going to be completely offline for the next two weeks, so I can't offer to coordinate/help in the short term. But, if anyone's really excited to get this in before D7 code freeze (just to be safe), they could follow the instructions I wrote over at Setting up a site to serve release history files used by the "Update status" module →
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since there has been no follow up to #51 going to close out as outdated. If still a request please reopen addressing #51 comment and updating issue summary for D10 and up.
Thanks!