#35719: NEW: minpack --------------------------+-------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: minpack | --------------------------+-------------------------------- Comment (by jjstickel@…): Replying to [comment:1 jmr@…]:

You don't need to handle the patchfile yourself just because it's remote and gzipped. Patchfiles that are not present in files/ will be fetched and applied automatically. They can also be gzipped.

This is helpful, but I am not sure how to implement it. Can you show me an example? Will the patchfile just be a url? -- Ticket URL: <https://trac.macports.org/ticket/35719#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35719: NEW: minpack --------------------------+-------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: minpack | --------------------------+-------------------------------- Comment (by macsforever2000@…): A few questions / issues: 1. Isn't this already in py-scipy? 1. I don't like the version handling. You hardcode it many times in the portfile. Since it is not used directly, why not use version "19961126" instead of "19961126.16" and call "16" the minor_version or similar and then use those variables throughout the portfile? 1. Do we really need gcc43 and gcc44 variants? Would anyone actually use that in a new port? -- Ticket URL: <https://trac.macports.org/ticket/35719#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35719: NEW: minpack --------------------------+-------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: minpack | --------------------------+-------------------------------- Comment (by jjstickel@…): Replying to [comment:4 macsforever2000@…]:

A few questions / issues:

1. Isn't this already in py-scipy?

Yes, but compiled using f2py (I think) specifically for use in python. I am creating this port so that the library can be linked from fortran programs (and I suppose c/c++, but I haven't tested).

1. I don't like the version handling. You hardcode it many times in the portfile. Since it is not used directly, why not use version "19961126" instead of "19961126.16" and call "16" the minor_version or similar and then use those variables throughout the portfile?

OK, I can do this. This is legacy code, and hence version numbers will only change if patches are necessary for compiling with modern compilers, but nonetheless I understand your request.

1. Do we really need gcc43 and gcc44 variants? Would anyone actually use that in a new port?

I can certainly remove gcc43 and gcc44 and add gcc48. I had copied these variants over from some other port. Thank you for your input. -- Ticket URL: <https://trac.macports.org/ticket/35719#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35719: NEW: minpack --------------------------+-------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: minpack | --------------------------+-------------------------------- Changes (by macsforever2000@…): * status: new => closed * resolution: => fixed Comment: Added in r106900 with gcc47-49. -- Ticket URL: <https://trac.macports.org/ticket/35719#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X