Re: port:qt5 and (proposed) port:qt5-kde cohabitation

On Thursday October 06 2016 23:19:38 Marko Käning wrote: Hi, > Currently the situation for port qt5-kde is as follows: > - 5 port groups would have to be updated (see comments 30-34 in [1]) That's a maximum, and this is the main point where we have to come to a consensus. I'll add that I

Re: port:qt5 and (proposed) port:qt5-kde cohabitation

Dear Qt folks, regarding René's post from March (see below) I believe it would be good to give a _short_ update on the qt5-kde port status. Currently the situation for port qt5-kde is as follows: - Qt at version 5.6.1 - tested building on Mavericks and El Capitan VMs - René also managed

Re: Issues with oudated ports / GitHub

Hi Eric, thanks for the pointer. Good to hear that things are already in motion to make the switch. I'm looking over the messages exchanged in the last couple of weeks. Best, Marcel On 16/10/06, Eric A. Borisch wrote: Marcel, At least some of your concerns should be getting addressed with

Re: Issues with oudated ports / GitHub

Hello Marcel, On 2016-10-06 19:12, Marcel Bischoff wrote: > I was advised that I should ask my questions and raise my issues here. > > I'm currently considering dropping the use of MacPorts altogether as > this projects' track record regarding critical updates of major software > tools is rather

Re: Issues with oudated ports / GitHub

On Oct 6, 2016, at 1:12 PM, Marcel Bischoff wrote: > I'm currently considering dropping the use of MacPorts altogether ok. > as > this projects' track record regarding critical updates of major software > tools is rather underwhelming. Furthermore, I'm asking myself

Re: Working with Git

On Oct 6, 2016, at 10:58AM, Rainer Müller wrote: > On 2016-10-06 09:33, Sterling Smith wrote: >> On Oct 5, 2016, at 7:53PM, Ryan Schmidt wrote: >> >>> Suppose a user submits an update to a port. >>> >>> With Subversion, the user would submit a

Re: [153575] trunk/dports/devel/gpgme/Portfile

On 10/6/16 4:54 AM, Ryan Schmidt wrote: > >> On Oct 4, 2016, at 3:40 PM, dev...@macports.org wrote: >> >> Revision >> 153575 >> Author >> dev...@macports.org >> Date >> 2016-10-04 13:40:24 -0700 (Tue, 04 Oct 2016) >> Log Message >> >> gpgme: deactivate kdepimlibs4 earlier than 4.14.3_4 in

Re: Working with Git

On 2016-10-06 09:33, Sterling Smith wrote: > On Oct 5, 2016, at 7:53PM, Ryan Schmidt wrote: > >> Suppose a user submits an update to a port. >> >> With Subversion, the user would submit a patch in a Trac ticket. To test it, >> I would download the patch and apply it to

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 2016-10-06, at 9:40 AM, René J.V. Bertin wrote: > > Wow ... have you also thought about my mom's old blue baby iMac G3 which > still runs AFAIK? :D And maybe providing a newer Mach kernel for them, too? Indeed, it's surprising to me as well sometimes just how useful these machines still

Re: Working with Git

On 2016-10-06 10:22, Ryan Schmidt wrote: > On Oct 6, 2016, at 02:33, Sterling Smith > wrote: >> When is the macports repo on GitHub supposed to appear? > > I have no ETA for you yet. "When it's ready." Part of being ready > includes having documentation about how we'll

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thu, Oct 6, 2016 at 12:49 PM, René J.V. Bertin wrote: > On Thursday October 06 2016 12:32:24 Brandon Allbery wrote: > Hasn't this become easier at all? > Only if you can use the GPL3 libstdc++. Since the stuff Apple ships doesn't, we lose. Linux of course does not have

Re: Working with Git

On Oct 6, 2016, at 1:22AM, Ryan Schmidt wrote: > On Oct 6, 2016, at 02:33, Sterling Smith wrote: >> >> Ryan, >> >>> On Oct 5, 2016, at 7:53PM, Ryan Schmidt wrote: >>> >>> >>> The user will submit a pull request. How

Issues with oudated ports / GitHub

Hi all, I was advised that I should ask my questions and raise my issues here. I'm currently considering dropping the use of MacPorts altogether as this projects' track record regarding critical updates of major software tools is rather underwhelming. Furthermore, I'm asking myself what use it

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 12:32:24 Brandon Allbery wrote: Hasn't this become easier at all? > now. At my previous job, when we ran into this we just lifted the whole > thing to glue multiple g++ releases to a common libstdc++ from Debian > (clang / libc++ wasn't an issue back then). Sounds

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 09:26:43 Ken Cunningham Webuse wrote: > 10.4 and 10.5 users who have PPC machines worth keeping might well have to > consider gcc cxx11options, if those systems are to have any path forward to > newer software. Wow ... have you also thought about my mom's old blue

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 2016-10-06, at 7:48 AM, Mojca Miklavec wrote: > On 6 October 2016 at 16:23, René J.V. Bertin wrote: >> >> Ken: apologies for not having thought of this, but myself when I was still >> running 10.6 I've had sufficient success with building C++11 code using a >> (then) recent gcc port. It's

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thu, Oct 6, 2016 at 12:25 PM, René J.V. Bertin wrote: > Actually, that hasn't yet caused me any problems on Linux. I've made the > v6 collection the default as soon as it became available, and certainly > haven't had to rebuild anything because of it. You haven't seen

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 16:48:44 Mojca Miklavec wrote: > This would probably mostly work fine if *all* ports were built with > g++ (= against the same version of mp-provided stdlibc++). I can > easily imagine problems when gcc is switched from, say, version 5 to > version 6, but let's ignore

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 6 October 2016 at 16:23, René J.V. Bertin wrote: > > Ken: apologies for not having thought of this, but myself when I was still > running 10.6 I've had sufficient success with building C++11 code using a > (then) recent gcc port. It's possible that things have evolved so much > nowadays

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 06:33:56 Ken Cunningham Webuse wrote: > Some of the builds on these older machines can take hours and hours... > webkit2-gtk is not even to be mentioned. Didn't even think of that yet, but yes. The problem is of course that we *are* indeed talking about older

Re: Working with Git

On 2016-10-06 14:28, Ryan Schmidt wrote: > If there are easy ways to rewrite the history of a pull request, by all > means, let's suggest the user do that, and provide instructions for how to do > so. I have no idea how to do it. You can rewrite the source branch of a pull request in any way

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> > The only blocking stone is meeting the agreement about how to > name the new binary archives [and implementing that] :) It would be nice if that discussion was finalized and a plan enacted. Some of the builds on these older machines can take hours and hours... webkit2-gtk is not even to be

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 6 October 2016 at 15:08, Ryan Schmidt wrote: > > Let's take the qt5-qtbase port as an example. It depends on the icu port. Its > library /opt/local/libexec/qt5/lib/QtCore.framework/QtCore links with icu's > libraries /opt/local/lib/libicui18n.55.dylib, > /opt/local/lib/libicuuc.55.dylib,

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:55 AM, Mojca Miklavec wrote: > > On 6 October 2016 at 14:43, Ryan Schmidt wrote: >>> On Oct 6, 2016, at 7:35 AM, Mojca Miklavec wrote: >>> >>> It works without https://trac.macports.org/wiki/LibcxxOnOlderSystems >>> (= setting libc++ to become your

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 6 October 2016 at 14:40, René J.V. Bertin wrote: > On Thursday October 06 2016 07:17:18 Ryan Schmidt wrote: > >> I don't understand... Those two paragraphs seem contradictory. You say it >> works without libc++, and that forcing libc++ would cause the ports to fail >> (on vanilla OS X <

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 6 October 2016 at 14:43, Ryan Schmidt wrote: >> On Oct 6, 2016, at 7:35 AM, Mojca Miklavec wrote: >> >> It works without https://trac.macports.org/wiki/LibcxxOnOlderSystems >> (= setting libc++ to become your default stdlib globally). But the >> port in question most likely still needs libc++.

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:35 AM, Mojca Miklavec wrote: > > It works without https://trac.macports.org/wiki/LibcxxOnOlderSystems > (= setting libc++ to become your default stdlib globally). But the > port in question most likely still needs libc++. > > Read as: if you use the

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:40 AM, René J.V. Bertin wrote: > >> We want to move the matter of determining that an error condition exists >> from the portfiles and portgroups to MacPorts base. Then it will be easier >> for the buildbot to query MacPorts base and ask if the port

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 07:17:18 Ryan Schmidt wrote: > I don't understand... Those two paragraphs seem contradictory. You say it > works without libc++, and that forcing libc++ would cause the ports to fail > (on vanilla OS X < 10.9), but then you say it would help to use libc++. I guess

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 6 October 2016 at 14:17, Ryan Schmidt wrote: >> On Oct 6, 2016, at 6:26 AM, Mojca Miklavec wrote: >> On 6 October 2016 at 12:06, René J.V. Bertin wrote: >>> On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: >>> If a port requires C++11 / libc++, include the cxx11 1.0 portgroup. >>>

Re: Working with Git

> On Oct 6, 2016, at 7:15 AM, Davide Liessi wrote: > > 2016-10-06 13:15 GMT+02:00 Ryan Schmidt : >> I assumed that in such a case, where the contributor is (or we are) making >> several commits to fix mistakes in a submission, we would use a

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 7:06 AM, René J.V. Bertin wrote: > > On Thursday October 06 2016 06:25:06 Ryan Schmidt wrote: > >> By including the portgroup, you are declaring that the port requires C++11. >> Users using "vanilla" OS X versions prior to 10.9 who try to install such

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 6:26 AM, Mojca Miklavec wrote: > > On 6 October 2016 at 12:06, René J.V. Bertin wrote: >> On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: >> >>> If a port requires C++11 / libc++, include the cxx11 1.0 portgroup. >> >> I

Re: Working with Git

2016-10-06 13:15 GMT+02:00 Ryan Schmidt : > I assumed that in such a case, where the contributor is (or we are) making > several commits to fix mistakes in a submission, we would use a "squash > merge" (?) to combine all the changes in the pull request into a single >

Re: [153554] trunk/dports/math/octave-database/Portfile

> On Oct 4, 2016, at 7:48 AM, m...@macports.org wrote: > > Revision > 153554 > Author > m...@macports.org > Date > 2016-10-04 05:48:43 -0700 (Tue, 04 Oct 2016) > Log Message > > octave-database: provide mysql variants, fix depends_lib. > Modified Paths > > •

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 06:25:06 Ryan Schmidt wrote: > By including the portgroup, you are declaring that the port requires C++11. > Users using "vanilla" OS X versions prior to 10.9 who try to install such a > port will receive an error message with a link to the wiki page explaining >

Re: Patch naming policy (was: Re: [153574] trunk/dports/sysutils/skey)

Hi, I don't care if we use *.diff or *.patch. Either is fine, but I would prefer if we would stick to one ending and try to be as consistent as we can be. The "patch-" prefix is a bit redundant indeed, but then again I don't care that much. I would be OK with removal, but again I would like to

Re: [153575] trunk/dports/devel/gpgme/Portfile

> On Oct 4, 2016, at 3:40 PM, dev...@macports.org wrote: > > Revision > 153575 > Author > dev...@macports.org > Date > 2016-10-04 13:40:24 -0700 (Tue, 04 Oct 2016) > Log Message > > gpgme: deactivate kdepimlibs4 earlier than 4.14.3_4 in pre_activate to avoid > a conflict (#52496). > Modified

Re: Working with Git

On 06/10/16 12:15, Ryan Schmidt wrote: On Oct 6, 2016, at 06:09, Chris Jones wrote: On 06/10/16 11:43, Mojca Miklavec wrote: On 6 October 2016 at 09:39, Chris Jones wrote: How do I take the user's pull request, make additional changes, and commit them to our

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On 6 October 2016 at 12:06, René J.V. Bertin wrote: > On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: > >> If a port requires C++11 / libc++, include the cxx11 1.0 portgroup. > > I wonder if that shouldn't simply be done by the Qt5 PortGroup then ... > > I don't

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Oct 6, 2016, at 05:06, René J.V. Bertin wrote: > >> On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: >> >> If a port requires C++11 / libc++, include the cxx11 1.0 portgroup. > > I wonder if that shouldn't simply be done by the Qt5 PortGroup then ... > > I

Re: Working with Git

On Oct 6, 2016, at 06:09, Chris Jones wrote: > > > >> On 06/10/16 11:43, Mojca Miklavec wrote: >> On 6 October 2016 at 09:39, Chris Jones wrote: How do I take the user's pull request, make additional changes, and commit them to our master? >>> >>> Anyone

Re: Working with Git

On 06/10/16 11:43, Mojca Miklavec wrote: On 6 October 2016 at 09:39, Chris Jones wrote: How do I take the user's pull request, make additional changes, and commit them to our master? Anyone can commit to the branch created by the user for the pull request. So you can just checkout that

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

On Thursday October 06 2016 04:35:02 Ryan Schmidt wrote: > If a port requires C++11 / libc++, include the cxx11 1.0 portgroup. I wonder if that shouldn't simply be done by the Qt5 PortGroup then ... I don't really follow what that portgroup does. Is there a risk of breaking anything when

Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

> On Oct 6, 2016, at 3:56 AM, René J.V. Bertin wrote: > > Hi, > > I got the attached build failure notifications, which in both cases I think > can be traced to the use of `-stdlib=libstdc++` : > > {{{ > [ 84%] Building CXX object

Re: Working with Git

On 06/10/16 10:19, Ryan Schmidt wrote: On Oct 6, 2016, at 4:02 AM, Chris Jones wrote: On 06/10/16 10:00, Ryan Schmidt wrote: On Oct 6, 2016, at 3:59 AM, Chris Jones wrote: Hi, The instructions at

Re: Working with Git

> On Oct 6, 2016, at 4:02 AM, Chris Jones wrote: > > > > On 06/10/16 10:00, Ryan Schmidt wrote: >> >>> On Oct 6, 2016, at 3:59 AM, Chris Jones wrote: >>> >>> Hi, >>> >>> The instructions at >>> >>>

Re: Working with Git

On 06/10/16 10:00, Ryan Schmidt wrote: On Oct 6, 2016, at 3:59 AM, Chris Jones wrote: Hi, The instructions at https://trac.macports.org/wiki/WorkingWithGit seem a little out of date w.r.t. forking. It says "To do that, go to ​https://github.com/macports/ports/

Re: Working with Git

> On Oct 6, 2016, at 3:59 AM, Chris Jones wrote: > > Hi, > > The instructions at > > https://trac.macports.org/wiki/WorkingWithGit > > seem a little out of date w.r.t. forking. It says > > "To do that, go to ​https://github.com/macports/ports/ and click the fork >

Re: Working with Git

Hi, The instructions at https://trac.macports.org/wiki/WorkingWithGit seem a little out of date w.r.t. forking. It says "To do that, go to ​https://github.com/macports/ports/ and click the fork button at the top right." but ​https://github.com/macports/ports/ does not exist, it gives a 404

dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

Hi, I got the attached build failure notifications, which in both cases I think can be traced to the use of `-stdlib=libstdc++` : {{{ [ 84%] Building CXX object src/CMakeFiles/dbusmenu-qt5.dir/utils.cpp.o cd

Re: Working with Git

> On Oct 6, 2016, at 03:32, Chris Jones wrote: > > > >> On 06/10/16 09:22, Ryan Schmidt wrote: >>> On Oct 6, 2016, at 02:33, Sterling Smith wrote: >>> >>> Ryan, >>> On Oct 5, 2016, at 7:53PM, Ryan Schmidt

Re: Working with Git

On 06/10/16 09:22, Ryan Schmidt wrote: On Oct 6, 2016, at 02:33, Sterling Smith wrote: Ryan, On Oct 5, 2016, at 7:53PM, Ryan Schmidt wrote: Suppose a user submits an update to a port. With Subversion, the user would submit a patch in a

Re: Working with Git

On Oct 6, 2016, at 02:33, Sterling Smith wrote: > > Ryan, > >> On Oct 5, 2016, at 7:53PM, Ryan Schmidt wrote: >> >> Suppose a user submits an update to a port. >> >> With Subversion, the user would submit a patch in a Trac ticket. To test it,

Re: Working with Git

Hi Ryan, - On 6 Oct, 2016, at 04:53, Ryan Schmidt ryandes...@macports.org wrote: > With Subversion, the user would submit a patch in a Trac ticket. To test it, I > would download the patch and apply it to my local Subversion working copy. If > I > like it, I commit it. If I don't like it, I

Re: Working with Git

> How do I take the user's pull request, make additional changes, and commit them to our master? Anyone can commit to the branch created by the user for the pull request. So you can just checkout that branch yourself, make changes, commit and push them back to the branch, and thus the merge

Re: Working with Git

Ryan, On Oct 5, 2016, at 7:53PM, Ryan Schmidt wrote: > Suppose a user submits an update to a port. > > With Subversion, the user would submit a patch in a Trac ticket. To test it, > I would download the patch and apply it to my local Subversion working copy. > If I