Opened 11 years ago

Closed 11 years ago

#39968 closed submission (fixed)

Create new port for py-fortranformat; Portfile attached

Reported by: smithsp (Sterling Smith) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: g5pw (Aljaž Srebrnič), petrrr
Port: py-fortranformat

Description (last modified by mf2k (Frank Schima))

I would like to submit a Portfile for a py-fortranformat port

Note that when I tested it, I had to change the name to py27-fortranformat to allow installation. I don't know if I missed a setting. I have changed it back to py-fortranformat. I am not sure what the livecheck.type setting is for.

Attachments (5)

Portfile (965 bytes) - added by mf2k (Frank Schima) 11 years ago.
Portfile.2 (1.4 KB) - added by smithsp (Sterling Smith) 11 years ago.
Revised portfile
Portfile.3 (1.4 KB) - added by smithsp (Sterling Smith) 11 years ago.
Updated portfile with revised categories
Portfile.4 (1.1 KB) - added by smithsp (Sterling Smith) 11 years ago.
Improved Portfile to use bitbucket.setup
Portfile.5 (1.2 KB) - added by smithsp (Sterling Smith) 11 years ago.
Revised the Portfile to explicitly state the master_sites and distname, since the project is not git-tagged.

Download all attachments as: .zip

Change History (14)

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

Description: modified (diff)
Keywords: python fortran format removed
Milestone: MacPorts Future
Version: 2.2.0

In the future, please attach your Portfile and do not set the Milestone field.

Changed 11 years ago by mf2k (Frank Schima)

Attachment: Portfile added

comment:2 in reply to:  1 Changed 11 years ago by smithsp (Sterling Smith)

Replying to macsforever2000@…:

In the future, please attach your Portfile and do not set the Milestone field.

Thanks for the feedback.

comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Please add the standard modeline as the first line, and conform to it (indentations at multiples of four spaces). Please add the "# $Id$" line as the second line, and a blank line after it.

Since this project is hosted at bitbucket, consider using the bitbucket 1.0 portgroup.

comment:4 Changed 11 years ago by mf2k (Frank Schima)

Also having only a single md5 checksum is not acceptable. The guidelines recommend rmd160 and sha256 at minimum.

Changed 11 years ago by smithsp (Sterling Smith)

Attachment: Portfile.2 added

Revised portfile

comment:5 Changed 11 years ago by cooljeanius (Eric Gallager)

Some more feedback:

  • There isn't currently an "io" category yet: http://www.macports.org/ports.php (or even a "fortran" one for that matter... although I could see arguments for adding the latter to a bunch of ports)

I am not sure what the livecheck.type setting is for.

The port livecheck command can tell if a port has been updated or not. With python ports we generally only livecheck the overall port, and not any of its subports.

Last edited 11 years ago by cooljeanius (Eric Gallager) (previous) (diff)

Changed 11 years ago by smithsp (Sterling Smith)

Attachment: Portfile.3 added

Updated portfile with revised categories

Changed 11 years ago by smithsp (Sterling Smith)

Attachment: Portfile.4 added

Improved Portfile to use bitbucket.setup

comment:6 Changed 11 years ago by g5pw (Aljaž Srebrnič)

Cc: g5pw@… added

Hmm... I'm afraid that if the repository is not tagged, you can't use bitbucket.setup like that. Try to contact the developer and ask him if he can tag releases.

comment:7 Changed 11 years ago by mf2k (Frank Schima)

Since the python portgroup already adds this port to the python category, we prefer to append the other categories.

categories-append   science print

Changed 11 years ago by smithsp (Sterling Smith)

Attachment: Portfile.5 added

Revised the Portfile to explicitly state the master_sites and distname, since the project is not git-tagged.

comment:8 Changed 11 years ago by petrrr

Cc: Peter.Danecek@… added

Cc Me!

comment:9 Changed 11 years ago by g5pw (Aljaž Srebrnič)

Resolution: fixed
Status: newclosed

Commited in r112748.

Note: See TracTickets for help on using tickets.