[MacPorts] #47887: New port cantera-devel
#47887: New port cantera-devel ------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: cantera-devel ------------------------+-------------------------------- 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. -- Ticket URL: <https://trac.macports.org/ticket/47887> MacPorts <https://www.macports.org/> Ports system for OS X
#47887: New port cantera-devel ----------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: cantera-devel | ----------------------------+-------------------------------- Comment (by larryv@…): If the portfiles are almost identical, maybe you should implement `cantera-devel` as a subport of `cantera`. See the `tmux` portfile for [[changeset:136253|an example]]. -- Ticket URL: <https://trac.macports.org/ticket/47887#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#47887: New port cantera-devel ----------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: cantera-devel | ----------------------------+-------------------------------- Comment (by 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. -- Ticket URL: <https://trac.macports.org/ticket/47887#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#47887: cantera-devel: New subport of cantera ----------------------------+---------------------- Reporter: macports@… | Owner: larryv@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: cantera-devel | ----------------------------+---------------------- Changes (by larryv@…): * status: new => assigned * owner: macports-tickets@… => larryv@… Comment: It’s fine, we can keep using this ticket. -- Ticket URL: <https://trac.macports.org/ticket/47887#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#47887: cantera-devel: New subport of cantera ----------------------------+---------------------- Reporter: macports@… | Owner: larryv@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: cantera-devel | ----------------------------+---------------------- Comment (by 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. -- Ticket URL: <https://trac.macports.org/ticket/47887#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#47887: cantera-devel: New subport of cantera ----------------------------+---------------------- Reporter: macports@… | Owner: larryv@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: cantera-devel | ----------------------------+---------------------- Comment (by macports@…): Hi, as cantera 2.2.0 was recently released, I changed the diff to also include the new version. -- Ticket URL: <https://trac.macports.org/ticket/47887#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#47887: cantera-devel: New subport of cantera ----------------------------+---------------------- Reporter: macports@… | Owner: larryv@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: cantera-devel | ----------------------------+---------------------- Changes (by larryv@…): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:4 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.ta... These files usually don’t contain the same files, but they might. It depends on the project. Feel free to ask on [[MailingLists|macports-dev]] if you have more questions. -- Ticket URL: <https://trac.macports.org/ticket/47887#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts