Review or Commit of #52814 scala2.12

[David Strawn]

Hey all,

Can I get a review or commit of this port?

URL: https://trac.macports.org/ticket/52814
Port: scala2.12
Stale: 4 weeks

Thanks,

David

Re: port requires c++1y -> use cxx11 portgroup?

[Ken Cunningham]

> 
> 
> The main thing you get is that, without that portgroup, it will attempt to 
> build on older OS X and fail. It also supports the 
> https://trac.macports.org/wiki/LibcxxOnOlderSystems 
>  workflow for those 
> users who have done it to get C++11 and later on older OS X versions.
> 

Exactly what is happening, according to buildbots (works great on 10.6.8 with 
libcxx tho).

I was just going to throw in the cxx11, but hey - I’m learning not to do stuff 
like that without asking permission.

K

Re: port requires c++1y -> use cxx11 portgroup?

[Brandon Allbery]

On Sat, Dec 3, 2016 at 3:42 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> thanks! should I add it now to Pingus, or leave it as it is do you think?


The main thing you get is that, without that portgroup, it will attempt to
build on older OS X and fail. It also supports the
https://trac.macports.org/wiki/LibcxxOnOlderSystems workflow for those
users who have done it to get C++11 and later on older OS X versions.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

Re: [macports-ports] branch master updated: pingus: new port submission

[Brandon Allbery]

On Sat, Dec 3, 2016 at 3:38 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> Yeah - that was interesting. The bin/pingus launch script had this:
>
> #!/bin/sh
> exec "/Applications/MacPorts/Pingus.app/Contents/MacOS/libexec/pingus"
> --datadir "/Applications/MacPorts/Pingus.app/Contents/MacOS/share/pingus"
> "$@"
>
> which works from a terminal prompt, but not in an application bundle.
>
> taking off the  "$@“ allowed the launch script to work in  the bundle.
>
> Do you know of a better method to use?
>

Get rid of any parameter that starts with the characters "-psn_". This is
added by the bundle launcher, expected by native applications, and will
confuse most Linux-originated programs.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

port requires c++1y -> use cxx11 portgroup?

[Ken Cunningham]

The pingus port I put up last night (and which Ryan so kindly fixed while I was 
sleeping for a missing dependency and an error on case-sensitive file systems - 
gotta love those buildbots for finding these things - and thanks for that) 
requires the c++1y standard to build. Builds will fail on systems that can't 
support this.

Would it be appropriate to use the cxx11 portgroup for this? For future 
reference, are there other standards (like c++14 perhaps) that should also use 
the cxx11 portgroup?

Thanks! -- Ken

Re: [RJVB/macstrop] use github ID for maintainer (2fb8aab)

[René J . V . Bertin]

Hi,

If I may add a few more cents to this topic (I understand things are still in 
flux):

In order to keep the maintainer lines a bit cleaner: would it be possible to 
consider a syntax where each maintainer has a single entry which just appends 
the github ID along the lines `currentlyusedID=githubID` (so cal=neverpanic or 
gmail.com:rjvbertin=RJVB)?

Regardless of how they're used on github I'd have avoided using the @ symbol in 
the maintainer syntax because of its use in email addresses. I would also only 
print the github IDs with `port -v info` because they seem to be of little 
interest to the average user who may only need to use the maintainer email 
address. (And I'd print the github ID on a single line with the email too, 
vertical screen space typically being more limited than horizontal space.)

R.