Re: OpenCoarrays Portfile ticket response?

> On Sep 30, 2015, at 10:44 PM, Damian Rouson > wrote: > > >> On Sep 30, 2015, at 9:47 PM, Eric A. Borisch > > wrote: >> >> Done. > > Please accept my sincerest apologies for being such a royal pain in the @$$, > but the tar ball that was posted was posted at

Re: OpenCoarrays Portfile ticket response?

> On Sep 30, 2015, at 9:47 PM, Eric A. Borisch wrote: > > Done. Please accept my sincerest apologies for being such a royal pain in the @$$, but the tar ball that was posted was posted at the link I provided previously was actually the pre-release version 2.0.0 when it should have been the re

Re: OpenCoarrays Portfile ticket response?

Done. On Wednesday, September 30, 2015, Damian Rouson < dam...@sourceryinstitute.org> wrote: > > > On Sep 30, 2015, at 5:50 PM, Brandon Allbery > wrote: > > On Wed, Sep 30, 2015 at 8:43 PM, Damian Rouson < > dam...@sourceryinstitute.org > > wrote: > >> Wow. I assume that means we’ll be in the n

Re: OpenCoarrays Portfile ticket response?

> On Sep 30, 2015, at 5:50 PM, Brandon Allbery wrote: > > On Wed, Sep 30, 2015 at 8:43 PM, Damian Rouson > wrote: > Wow. I assume that means we’ll be in the next release. Hooray! Thanks for > the great news. It’s time to open a bottle of champagne. > >

Re: OpenCoarrays Portfile ticket response?

> On Sep 30, 2015, at 5:50 PM, Brandon Allbery wrote: > > On Wed, Sep 30, 2015 at 8:43 PM, Damian Rouson > wrote: > Wow. I assume that means we’ll be in the next release. Hooray! Thanks for > the great news. It’s time to open a bottle of champagne. >

Re: OpenCoarrays Portfile ticket response?

On Wed, Sep 30, 2015 at 8:43 PM, Damian Rouson wrote: > Wow. I assume that means we’ll be in the next release. Hooray! Thanks > for the great news. It’s time to open a bottle of champagne. Port updates are completely independent of MacPorts releases. If it's been committed to the tree, it s

Re: OpenCoarrays Portfile ticket response?

> On Sep 30, 2015, at 5:19 PM, Eric A. Borisch wrote: > > I've committed up a working (I believe) version. Wow. I assume that means we’ll be in the next release. Hooray! Thanks for the great news. It’s time to open a bottle of champagne. :D _

Re: OpenCoarrays Portfile ticket response?

I've committed up a working (I believe) version. On Friday, September 25, 2015, Damian Rouson wrote: > * PING *** > > > > On Sep 21, 2015, at 11:31 PM, Mojca Miklavec > wrote: > > > > On Tue, Sep 22, 2015 at 7:27 AM, Damian Rouson wrote: > >> Alessandro Fanfarillo submitted a Portfile f

Re: macports-dev Digest, Vol 109, Issue 41

On 30.09.2015 07:09 PM, Damian Rouson wrote: > Yes, please include the OpenCoarrays port if at all possible! We’ve > responded to every concern raised in the 4 months since we first submitted > the Portfile. In that time frame, we have released OpenCoarrays 1.0.0, > 1.0.1, and 1.0.2. We’re getti

Re: macports-dev Digest, Vol 109, Issue 41

> On Sep 30, 2015, at 8:42 AM, macports-dev-requ...@lists.macosforge.org wrote: > > Date: Wed, 30 Sep 2015 23:09:20 +1000 > From: Joshua Root > To: MacPorts Development > Subject: Any more changes to merge for 2.3.4? > > > Is there anything else we should get in before tagging 2.3.4? Yes, p

Re: Any more changes to merge for 2.3.4?

That is not going to happen any time soon unless you are willing to write up a port to provide the as-wrapper as an alternative to cctools. I don't want the MacPorts clang falling back on the Xcode toolchains when -no-integrated-as is used. C.f. the entire thread about reproducible builds...

Re: Any more changes to merge for 2.3.4?

Joshua, One issue which doesn't seem to be addressed yet in the svn package set is to make sure that no package forces a dependency on cctools when Xcode 7 in installed. IHMO, this is undesirable behavior because it regresses the enhanced modern opcode support in the new clang-based assemble

Re: Any more changes to merge for 2.3.4?

Joshua, The glew package needs the fix I proposed in https://trac.macports.org/attachment/ticket/49004/Portfile.diff to avoid the Apple clang 7.0 compiler hangs with Xcode 7. Jack On Wed, Sep 30, 2015 at 9:09 AM, Joshua Root wrote: > Is there anything else we should get in before

Re: Issue with the portgroup python using the python.version variable

You may also be interested in the pypi2port contrib. I've not started using it much yet, but I'm planning to at some point. sudo port install py27-progressbar svn co https://svn.macports.org/repository/macports/contrib/pypi2port/ Russell On 25/09/15 13:03, Tiago Freitas Pereira wrote: Ah, I g

Any more changes to merge for 2.3.4?

Is there anything else we should get in before tagging 2.3.4? - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev