Re: Tcl list-related 2.3.4 -> 2.3.5 changes?

On Saturday December 03 2016 12:47:47 Joshua Root wrote: Hi, >This was wrong all along. The enclosing braces on >{${nprefix} ${macports::prefix}} >mean that no substitution will happen, so you're mapping between those >literal strings. You want [list ${nprefix} ${macports::prefix}] instead. Doh

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

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=git

Re: Your message to macports-changes awaits moderator approval

On 2016-12-03 08:53, Mojca Miklavec wrote: > On 2 December 2016 at 14:55, Rainer Müller wrote: >> On 2016-12-02 12:28, Mojca Miklavec wrote: >> >>> But there might be some issues. Looking at a random commit email: >>> >>> https://lists.macports.org/pipermail/macports-changes/2016-December/14472

Re: Your message to macports-changes awaits moderator approval

On 2016-12-02 14:55, Rainer Müller wrote: > Yes, this is a problem on our end, probably occurring since I deployed > the From: addresses [1] after the discussion in [2]. > > After this, some mails were rejected by mailman, which we only > discovered a few days ago. To avoid losing any change mails

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

Hi, On Sat, Dec 03, 2016 at 11:35:21AM +0100, René J.V. Bertin wrote: > If I may add a few more cents to this topic (I understand things are > still in flux): This has been implemented in released in 2.3.5 already, so there's no flux and we get to keep what we currently have. I haven't gotten ar

Re: Your message to macports-changes awaits moderator approval

> On Dec 2, 2016, at 7:55 AM, Rainer Müller wrote: > > HTML was a request for the new commit mails. I was not able to find > anything better than git-multimail [3], but it only supports either text > or HTML. Unfortunately, It does not support sending both as MIME > multi-part alternatives as th

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

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 sys

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

> On Dec 3, 2016, at 6:01 AM, Ken Cunningham > wrote: > > tobypeterson pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/d9673942b719a31aee1623f64d765e57de401dc5 > >

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

On Sat, Dec 3, 2016 at 3:20 PM, Lawrence Velázquez wrote: > +reinplace "s|\"$@\"||g" > ${destroot}${applications_dir}/Pingus.app/Contents/MacOS/pingus+} > > This is…strange. What exactly are you replacing here? > Likely making it not pass the (automatically generated and passed) session ID

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

Hi Larry, Thanks for the feedback. Apparently Pingus is very popular, and not on homebrew! A scoop! Hope people enjoy it (or at least their kids do). > This should be "GPL-3+”. Ah. I saw this

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

> On Dec 3, 2016, at 2:09 PM, Ken Cunningham > wrote: > > 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 tha

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

> > C++1y and C++14 are the same. Apparently not exactly the same — somewhere in Pingus or its included bits there was a specific note about changing back to c++1y as some compilers accepted that but not c++14. > > The cxx11 portgroup does not express the correct restrictions for C++14, > but

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

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/Conte

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

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

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

> > > 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 ge

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

On Sat, Dec 3, 2016 at 3:43 PM, Brandon Allbery wrote: > > 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. I should note that doing this properly is much

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

> On Dec 3, 2016, at 3:42 PM, Ken Cunningham > wrote: > >> C++1y and C++14 are the same. > > Apparently not exactly the same — somewhere in Pingus or its included > bits there was a specific note about changing back to c++1y as some > compilers accepted that but not c++14. "C++1y" was the work

Review or Commit of #52814 scala2.12

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: [macports-ports] branch master updated: sqlite3: revert to editline

You didn't remove the readline dependency. vq > On Dec 3, 2016, at 10:21 PM, Marius Schamschula wrote: > > Marius Schamschula (Schamschula) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/b510ccebf141f1f4e0e9275a2cab0baa28f