a-port-devel: what is the good practice

2013-10-04 Thread Joël Brogniart
Hello, I'd like to add a new port for the developer version of the auto-multiple-choice application based on a recent subversion version. What are the best practices? - Should I define the port for the last subversion revision or for a specific revision? - If the port is defined for a

Re: a-port-devel: what is the good practice

2013-10-04 Thread Ryan Schmidt
On Oct 4, 2013, at 02:07, Joël Brogniart wrote: I'd like to add a new port for the developer version of the auto-multiple-choice application based on a recent subversion version. What are the best practices? - Should I define the port for the last subversion revision or for a specific

Re: suggestion for Fortran recipe

2013-10-04 Thread Jeremy Huddleston Sequoia
Yeah, that sounds reasonable. As for the PortGroup, IIRC, someone was working on a general compilers PortGroup which would incorporate this. On Oct 3, 2013, at 18:47, David Strubbe dstru...@mit.edu wrote: Hi Jeremy and others, I think a few lines can be simplified in the new Fortran

Re: suggestion for Fortran recipe

2013-10-04 Thread Eric Gallager
I think it was Sean Farley, so I'm explicitly adding him on cc to this conversation... On Fri, Oct 4, 2013 at 10:32 AM, Jeremy Huddleston Sequoia jerem...@macports.org wrote: Yeah, that sounds reasonable. As for the PortGroup, IIRC, someone was working on a general compilers PortGroup

New wiki page describing commit rules needed or nonsense?

2013-10-04 Thread MK-MacPorts
I figured that a section about rules concerning properly formatted commit messages are missing in the wiki (not to talk about the Guide), which is why I created the following page: https://trac.macports.org/wiki/CommitRules below the committers guide

[111870] trunk/dports/devel/kmm_banking/Portfile

2013-10-04 Thread Joshua Root
Revision: 111870 https://trac.macports.org/changeset/111870 Author: mk at macports.org Date: 2013-10-04 11:16:26 -0700 (Fri, 04 Oct 2013) Log Message: --- kmm_banking: revert change made in r111867, because aqbanking5 isn't usable with kmm_banking [make use of

Re: [MacPorts] XcodeVersionInfo deleted version

2013-10-04 Thread Jeremy Lavergne
After some version, the OS is now OS X and no longer Mac OS X ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] XcodeVersionInfo deleted version

2013-10-04 Thread Eric Gallager
Yeah, that's Mountain Lion On Fri, Oct 4, 2013 at 2:47 PM, Jeremy Lavergne jer...@lavergne.gotdns.orgwrote: After some version, the OS is now OS X and no longer Mac OS X ___ macports-dev mailing list macports-dev@lists.macosforge.org

Re: [111870] trunk/dports/devel/kmm_banking/Portfile

2013-10-04 Thread MK-MacPorts
On Oct 4, 2013, at 8:41 PM, Joshua Root wrote: Why bump the revision when it fails to build either way? If this depends on a port that no longer exists, shouldn't it just be deleted? (If anyone has an older version of aqbanking installed, it will be automatically deactivated and replaced with

Re: [MacPorts] XcodeVersionInfo deleted version

2013-10-04 Thread Ryan Schmidt
On Oct 4, 2013, at 15:38, Eric Gallager wrote: On Fri, Oct 4, 2013 at 2:47 PM, Jeremy Lavergne wrote: After some version, the OS is now OS X and no longer Mac OS X Yeah, that's Mountain Lion My understanding is that Apple retroactively renamed Lion from Mac OS X to OS X, hence I changed the

Compile/Link 101

2013-10-04 Thread Craig Treleaven
Could someone please explain some very basic stuff about compiling/linking C and C++ code? For a new version of Myth, the configure script succeeds with XCode 5 on Mtn Lion and _fails_ with XCode 4.3 on Lion. The bit that I'm looking at just tests whether certain libraries (faac in this

Re: Compile/Link 101

2013-10-04 Thread Lawrence Velázquez
On Oct 4, 2013, at 9:39 PM, Craig Treleaven ctrelea...@cogeco.ca wrote: I actually don't know how the test _can succeed_ with XCode 5? There is no '-L' flag to indicate that the library is under /opt/local/lib. MacPorts sets the LIBRARY_PATH environment variable in the configure phase,