cantera-devel: New subport of cantera

[macports@…]

portfile for the latest published beta version of cantera.

Essentially, only version number and checksums are different from the original cantera portfile. The option 'python_old', which is unsupported in cantera 2.2, is removed.

I will create a patch for the stable cantera port which declares a conflict with cantera-devel as soon as cantera-devel is accepted.

[macports@…]

Portfile cantera-devel

[larryv (Lawrence Velázquez)]

If the portfiles are almost identical, maybe you should implement cantera-devel as a subport of cantera. See the tmux portfile for an example.

[macports@…]

Yes, this would be a much better way. Thank you for the hint, I didn't know about the subport feature. I'll create a new ticket for the improvement in the cantera port. Please close this ticket.

[larryv (Lawrence Velázquez)]

It’s fine, we can keep using this ticket.

[macports@…]

OK, I added a patch for the main cantera port which includes cantera-devel as a subport. Everything is quite straigt-forward, except that I had to remove the line github.tarball_from releases from the original port. However, I don't know why this line got there in the first place, and what its advantage is. The original cantera port builds fine also without that line.

[macports@…]

Portfile-cantera.diff

[macports@…]

Hi, as cantera 2.2.0 was recently released, I changed the diff to also include the new version.

[larryv (Lawrence Velázquez)]

Replying to macports@…:

OK, I added a patch for the main cantera port which includes cantera-devel as a subport.

Thanks, but I had to redo the patch. Since the github.setup proc sets several portfile options, it needs to be called near the beginning. Otherwise it overrides the settings from the rest of the portfile.

r137350 and r137351

Everything is quite straigt-forward, except that I had to remove the line github.tarball_from releases from the original port. However, I don't know why this line got there in the first place, and what its advantage is. The original cantera port builds fine also without that line.

It changes the location from which MacPorts fetches the source code:

• github.tarball_from tags (default): ​https://github.com/Cantera/cantera/archive/v2.2.0.tar.gz
• github.tarball_from releases: ​https://github.com/Cantera/cantera/releases/download/v2.2.0/cantera-2.2.0.tar.gz

These files usually don’t have the same contents, but they might. It depends on the project. Feel free to ask on macports-dev if you have more questions.