Opened 9 years ago

Closed 9 years ago

#47395 closed enhancement (fixed)

cantera: download from github

Reported by: macports@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version:
Keywords: maintainer haspatch Cc:
Port: cantera

Description

Cantera is moving to GitHub (see https://groups.google.com/forum/?fromgroups#!topic/cantera-users/-JyScUZm0O0)

This update just changes the download source.

Attachments (2)

cantera_patch_portfile.diff (626 bytes) - added by macports@… 9 years ago.
Cantera 2.1.2 on GitHub - Diff
Portfile-cantera.diff (1.1 KB) - added by macports@… 9 years ago.
Cantera 2.1.2 on GitHub - Diff

Download all attachments as: .zip

Change History (8)

Changed 9 years ago by macports@…

Attachment: cantera_patch_portfile.diff added

Cantera 2.1.2 on GitHub - Diff

comment:1 Changed 9 years ago by mf2k (Frank Schima)

Cc: mf2k@… removed
Keywords: maintainer added
Type: updateenhancement
Version: 2.3.3

Thanks! Per the guidelines, please use a unified diff format for your patch.

comment:2 Changed 9 years ago by macports@…

Thank you for pointing me to the right paragraph in the guidelines!

comment:3 Changed 9 years ago by larryv (Lawrence Velázquez)

I haven’t looked at this at all, but make sure that you don’t have to account for a stealth update here (PortfileRecipes#stealth-updates).

Changed 9 years ago by macports@…

Attachment: Portfile-cantera.diff added

Cantera 2.1.2 on GitHub - Diff

comment:4 Changed 9 years ago by macports@…

Thanks, that should definitely be there! I added that line.

comment:5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: haspatch added
Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned
Summary: Update cantera port for new sourcecantera: download from github

If a stealth update had occurred, the checksums would have changed, but you did not indicate changed checksums. In fact the checksums do change if we use your patch as-is, because your patch makes the port download from a tarball automatically generated by github from the git repository. Since this project also offers release downloads, we should use those instead, by using github.tarball_from releases. The checksums match those from sourceforge, so no stealth update has occurred and there is no need to change the dist_subdir.

Note also that the github.setup line is meant to replace, not supplement, the name and version lines; you would only keep the name or version lines if their values differed from those specified in the github.setup line, but in this case (and in most cases) they don't.

The cantera web site still tells people to download from SourceForge. You might want to let them know they should update that to refer people to github instead.

comment:6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.