Re: Working with Git

2016-10-07 19:34 GMT+02:00 Brandon Allbery : > I only wish other projects actually did this... rewriting history is > regrettably common in some projects. Sigh. Rewriting history in the master branch (or any branch intended to live long) should never be allowed. On the other

Re: tcl question: defining dynamically named variables in a namespace

On Friday October 07 2016 14:25:11 David Bariod wrote: Hi, Yes, something like that could work, but it may be a bit less trivial than that. R. >It's been a long time I haven't done Tcl development, but from memory: > >namespace eval { > --> your code here <--- >} > >should do what you're

Re: [153656] trunk/dports/devel/nodejs4

> On Oct 6, 2016, at 4:52 PM, ciserl...@macports.org wrote: > > Revision > 153656 > Author > ciserl...@macports.org > Date > 2016-10-06 14:52:24 -0700 (Thu, 06 Oct 2016) > Log Message > > nodejs4: update to version 4.5.0; add patch to fix compilation on darwin > version 13 or higher > Modified

Bacula Ticket 49203

Hi all, 6 months ago, I supplied patches to fix https://trac.macports.org/ticket/49203 . None of the committers applied the fixes, therefore may someone please apply them? Also, please remove me as maintainer from Bacula port file, as it is of no fun

Re: [153647] trunk/dports/devel/dbusmenu-qt/Portfile

> On Oct 6, 2016, at 1:11 PM, m...@macports.org wrote: > > Revision > 153647 > Author > m...@macports.org > Date > 2016-10-06 11:11:52 -0700 (Thu, 06 Oct 2016) > Log Message > > dbusmenu-qt5: upgrade to more recent version and add comments > Modified Paths > > •

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: > > Currently, once they find out about svn, and trac We will still use Trac for issue tracking, although I believe someone is looking into integrating GitHub sign in. vq ___

Re: reinplace permission denied mariadb-server

> On Oct 7, 2016, at 8:09 AM, Ryan Schmidt wrote: > > >> On Oct 7, 2016, at 9:48 AM, Bradley Giesbrecht wrote: >> >> Hi, >> >> >> mariadb-server is a support of mariadb. >> >> >> In post-extract I copy a file from filespath and in post-patch

Re: Issues with oudated ports / GitHub

On 16/10/07, Brandon Allbery wrote: On Fri, Oct 7, 2016 at 2:38 PM, Daniel J. Luke wrote: the cool kids also aren't writing 'tcl' these days ... ...but the way they write anything else, they might as well be writing fortran... Let me just chime in here and say that

Re: Working with Git

On Oct 7, 2016, at 2:20PM, Brandon Allbery wrote: > > On Fri, Oct 7, 2016 at 5:11 PM, Davide Liessi wrote: > On the other hand there is nothing wrong in rewriting history in a > temporary development branch (such as a branch for a pull request) >

Re: Issues with oudated ports / GitHub

On 2016-10-07 18:25, Ken Cunningham wrote: > The current "port update" ticket queue I find to be a rather > unpredictable mixture of requests of port updates, requests for new > ports, announcements that somebody has noticed a version update has > come available, and finished port updates awaiting

Re: Issues with oudated ports / GitHub

On 16/10/07, Ryan Schmidt wrote: After all, MacPorts maintainers are just some people devoting their free time to writing Portfiles. Sometimes other stuff in life stops them from responding to tickets or addressing certain issues. This is a given. Open source projects are mostly staffed by

Re: Issues with oudated ports / GitHub

On 16/10/07, Ryan Schmidt wrote: While the latter examples are just minor differences, especially things like ghc, fontforge an pandoc are either completely broken and/or severely outdated. I'm not trying to badmouth anyone or anything, just pointing to the higher (successful) update rate in

Re: Issues with oudated ports / GitHub

On 16/10/07, Ken Cunningham wrote: And there are "requests for ports" ( I think this means new requests for ports that don’t presently exist, mostly) that go back 11 years. Port submissions that go back the same length of time. Possibly some kind of massive clean-out of the old, dead,

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 1:23 PM, Marcel Bischoff wrote: > > On 16/10/07, Guido Soranzio wrote: > [...] >> I really hope that the migration of MacPorts to GitHub will trigger a >> collaboration between the two communities at last. How would our switching to GitHub

Re: Issues with oudated ports / GitHub

> On 7 Oct 2016, at 6:08 pm, Daniel J. Luke wrote: > > On Oct 7, 2016, at 11:59 AM, Marcel Bischoff wrote: It pains me to say that Homebrew is running circles around MacPorts in the department of current available packages. >>> >>>

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 12:07 PM, Marcel Bischoff wrote: > > On 16/10/07, Ryan Schmidt wrote: >>> While the latter examples are just minor differences, especially >>> things >>> like ghc, fontforge an pandoc are either completely broken and/or >>> severely outdated. I'm

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

> On Oct 6, 2016, at 12:49 PM, René J.V. Bertin wrote: > >> On Thursday October 06 2016 12:32:24 Brandon Allbery wrote: >> >> 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 >>

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 10:59 AM, Marcel Bischoff wrote: > >>> It pains me to say that Homebrew is running circles around MacPorts in >>> the department of current available packages. >> >> [citation needed] ;-) > > Gladly. I have written a small script to check that.

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 10:23 AM, Marcel Bischoff wrote: > >>> Just today I commented on a ticket that is six weeks old, about an >>> update to nodejs4. Version 4.5.0 was released on 16-Aug-2016, version >>> 4.6.0 on 27-Sep-2016. Version 4 is considered the stable LTS

Re: Working with Git

> On Oct 7, 2016, at 12:16 PM, Sterling Smith wrote: > > > On Oct 7, 2016, at 7:20AM, Chris Jones wrote: >> >> My point still stands though, you have to actively try the things you need >> to do, to get used to them. > +1 Yabut, then you

Re: Working with Git

On 07/10/16 17:39, Craig Treleaven wrote: On Oct 7, 2016, at 12:16 PM, Sterling Smith wrote: On Oct 7, 2016, at 7:20AM, Chris Jones wrote: My point still stands though, you have to actively try the things you need to do, to get used to

Re: Issues with oudated ports / GitHub

On Oct 7, 2016, at 11:59 AM, Marcel Bischoff wrote: >>> It pains me to say that Homebrew is running circles around MacPorts in >>> the department of current available packages. >> >> [citation needed] ;-) > > Gladly. I have written a small script to check that. Here are

Re: Working with Git

On 16/10/07, Brandon Allbery wrote: On Fri, Oct 7, 2016 at 12:43 PM, Chris Jones wrote: On 07/10/16 17:39, Craig Treleaven wrote: On Oct 7, 2016, at 12:16 PM, Sterling Smith wrote: On Oct 7, 2016, at 7:20AM, Chris Jones

Re: Working with Git

On Fri, Oct 7, 2016 at 1:31 PM, Marcel Bischoff wrote: > 'push --force' should *never* be used when working in a team except for > dire emergencies like having cleaned the history of accidentally > committed login credentials or the like. > I only wish other projects

Re: Issues with oudated ports / GitHub

> > The problem is: somebody needs to do the correct work to update each of those > ports to the latest version. In many cases, tickets are already filed, and > you can look them up to see what the current status is; if you don't find a > ticket, please file a new one. Couple of points

Re: Issues with oudated ports / GitHub

>> On Oct 7, 2016, at 10:59 AM, Marcel Bischoff wrote: >> It pains me to say that Homebrew is running circles around MacPorts in the department of current available packages. >>> >>> [citation needed] ;-) >> >> Gladly. I have written a small script to check

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 12:05 PM, Rainer Müller wrote: > > We are currently using the type field with "defect", "enhancement", > "update", "submission", "request". A ticket should be filed with the > appropriate type. > > To indicate a patch is attached to the ticket, we add

Re: Issues with oudated ports / GitHub

On 16/10/07, Guido Soranzio wrote: [...] I really hope that the migration of MacPorts to GitHub will trigger a collaboration between the two communities at last. That would be swell, indeed. Although I can't shake the feeling that it could be a clash of cultures. Kind of like old school coders

Re: Issues with oudated ports / GitHub

On Oct 7, 2016, at 1:18 PM, Marcel Bischoff wrote: > Thank you, this is a good illustration of what I mean when I write > MacPorts feels "stale", "dry" and "dated" when actually it is none of > those things. Having tickets open for 11 years does not inspire > confidence

Re: Working with Git

> On Oct 7, 2016, at 12:34 PM, Brandon Allbery wrote: > > On Fri, Oct 7, 2016 at 1:31 PM, Marcel Bischoff > wrote: > 'push --force' should *never* be used when working in a team except for > dire emergencies like having cleaned the history of

Re: Patch naming policy

> On Oct 6, 2016, at 12:04 PM, Rainer Müller wrote: > > On 2016-10-06 13:56, Mojca Miklavec wrote: >> 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. > > Some

Re: Working with Git

Hi, There will always be problems with the transition to GitHub that can be discussed on the mailing list to find a common solution. Then it can be documented to point people to that if they have the same problem. Yes. But I want to at least know how to perform the tasks that I currently

Re: review requested - widelands 1.9 update

> On Oct 7, 2016, at 10:08 AM, Ken Cunningham Webuse > wrote: > > I think this one looks ready for prime time. > > https://trac.macports.org/ticket/52188 I had been working on that, and have further changes locally not mentioned in the ticket.

Re: reinplace permission denied mariadb-server

> On Oct 7, 2016, at 9:48 AM, Bradley Giesbrecht wrote: > > Hi, > > > mariadb-server is a support of mariadb. > > > In post-extract I copy a file from filespath and in post-patch I patch the > file with reinplace: > port cat mariadb-server: > ... >post-extract { >

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

> On Oct 7, 2016, at 11:11 AM, René J.V. Bertin wrote: > > On Friday October 07 2016 10:51:59 Lawrence Velázquez wrote: > >> Not to mention the fact that literally every single C++ port would have >> to declare a library dependency on libgcc. > > Or not: if a compiler

Re: Working with Git

> On Oct 6, 2016, at 12:36 PM, Rainer Müller wrote: > > 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.

review requested - widelands 1.9 update

I think this one looks ready for prime time. https://trac.macports.org/ticket/52188 thanks Ken ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Working with Git

On Oct 7, 2016, at 7:20AM, Chris Jones wrote: > > My point still stands though, you have to actively try the things you need to > do, to get used to them. +1 > ___ > macports-dev mailing list >

review request - hatari 1.9 fix for snow leopard without xcode 4.2

I think this does it. https://trac.macports.org/ticket/52537 Thanks! Ken ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Issues with oudated ports / GitHub

It looks like others have already responded to most of your points, but I would just add: On Oct 6, 2016, at 12:12 PM, Marcel Bischoff wrote: > But if I still > cannot install (for example) pandoc because ghc still requires llwm-3.5 > which does not compile on Sierra: what choice do I have? I

Re: Issues with oudated ports / GitHub

On 16/10/06, Rainer Müller wrote: 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

Of C++ (and other) runtimes

On Friday October 07 2016 11:43:48 Lawrence Velázquez wrote: [was Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++] > it might be useful to refine this mechanism to allow something like > "configure.compiler.cxx macports-gcc-XYZ", which would add a direct >

Re: review requested - widelands 1.9 update

Very sorry -- couldn't tell. Thought it fell off the radar! K On 2016-10-07, at 8:10 AM, Ryan Schmidt wrote: > >> On Oct 7, 2016, at 10:08 AM, Ken Cunningham Webuse >> wrote: >> >> I think this one looks ready for prime time. >> >>

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

On Friday October 07 2016 10:51:59 Lawrence Velázquez wrote: > Not to mention the fact that literally every single C++ port would have > to declare a library dependency on libgcc. Or not: if a compiler selection mechanism is used that picks a macports-gcc version that dependency would be added

Re: Issues with oudated ports / GitHub

On 16/10/07, Ryan Schmidt wrote: It looks like others have already responded to most of your points, but I would just add: On Oct 6, 2016, at 12:12 PM, Marcel Bischoff wrote: But if I still cannot install (for example) pandoc because ghc still requires llwm-3.5 which does not compile on

Re: Working with Git

> On Oct 7, 2016, at 7:54 AM, Ryan Schmidt wrote: > > >> On Oct 6, 2016, at 12:36 PM, Rainer Müller wrote: >> >> On 2016-10-06 10:22, Ryan Schmidt wrote: >>> On Oct 6, 2016, at 02:33, Sterling Smith >>> wrote: When

Re: Working with Git

> On Oct 7, 2016, at 9:04 AM, Chris Jones wrote: > > Hi, > >>> There will always be problems with the transition to GitHub that can be >>> discussed on the mailing list to find a common solution. Then it can be >>> documented to point people to that if they have the

reinplace permission denied mariadb-server

Hi, mariadb-server is a support of mariadb. In post-extract I copy a file from filespath and in post-patch I patch the file with reinplace: port cat mariadb-server: ... post-extract { file mkdir ${worksrcpath}/macports copy ${filespath}/org.macports.mysql-server.plist

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

> On Oct 6, 2016, at 10: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 >>

Re: Issues with oudated ports / GitHub

On 16/10/06, Daniel J. Luke wrote: [...] If installing software by hand results in more current and more secure software for my development machine, I don't get the point of using MacPorts in the first place. MacPorts provides a way to save the 'recipe' for installing software (and a handy

Re: Of C++ (and other) runtimes

> On Oct 7, 2016, at 11:59 AM, René J.V. Bertin wrote: > > On Friday October 07 2016 11:43:48 Lawrence Velázquez wrote: > > [was Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because > of using libstdc++] > >> it might be useful to refine this mechanism to

Re: Working with Git

On 06/10/16 14:57, Rainer Müller wrote: 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

Re: Issues with oudated ports / GitHub

> On 7 Oct 2016, at 7:40 pm, Lawrence Velázquez wrote: > >> On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >> >> Currently, once they find out about svn, and trac > > We will still use Trac for issue tracking, although I believe someone is >

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 2:58 PM, Christopher Jones > wrote: > >> On 7 Oct 2016, at 7:40 pm, Lawrence Velázquez wrote: >> >>> On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >>> >>> Currently, once they find out about svn,

Re: Issues with oudated ports / GitHub

On Fri, Oct 7, 2016 at 2:38 PM, Daniel J. Luke wrote: > the cool kids also aren't writing 'tcl' these days ... ...but the way they write anything else, they might as well be writing fortran... -- brandon s allbery kf8nh sine nomine associates

Re: Issues with oudated ports / GitHub

> On 7 Oct 2016, at 8:08 pm, Lawrence Velázquez wrote: > >> On Oct 7, 2016, at 2:58 PM, Christopher Jones >> wrote: >> >>> On 7 Oct 2016, at 7:40 pm, Lawrence Velázquez wrote: >>> On Oct 7, 2016, at 2:09 PM, Chris

Re: Issues with oudated ports / GitHub

On 2016-10-07, at 10:05 AM, Rainer Müller wrote: > I am not sure how we could change these to make triaging trickets easier. I can't easily just look at the list and see what are new requests for ports to be included in macports. It all mixed in with other things. Also, the committer time

Re: Issues with oudated ports / GitHub

> On 7 Oct 2016, at 7:38 pm, Daniel J. Luke wrote: > > On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >>> moving to GitHub doesn't magically make more interested parties make >>> quality contributions. >> >> I agree that moving to github is not

Re: Issues with oudated ports / GitHub

> On 7 Oct 2016, at 8:12 pm, Ryan Schmidt wrote: > > >> On Oct 7, 2016, at 1:40 PM, Lawrence Velázquez wrote: >> >>> On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >>> >>> Currently, once they find out about svn, and

Re: review requested - widelands 1.8 update

Oh - I should say -- if there is anything about that last widelands portfile you'd like me to work on, just mention it. (I guess my email said 1.9, but the portfile is for 1.8) The next version of widelands (1.9) is up for fairly imminent release now as well, and so I'm working on that one now

Re: Issues with oudated ports / GitHub

On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >> moving to GitHub doesn't magically make more interested parties make quality >> contributions. > > I agree that moving to github is not going to suddenly make people where not > not previously looking for a packaging

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 1:40 PM, Lawrence Velázquez wrote: > >> On Oct 7, 2016, at 2:09 PM, Chris Jones wrote: >> >> Currently, once they find out about svn, and trac > > We will still use Trac for issue tracking, although I believe someone is >

Re: Working with Git

On 2016-10-07 19:00, Brandon Allbery wrote: > On Fri, Oct 7, 2016 at 12:43 PM, Chris Jones > wrote: > > Indeed, I was a little dubious of the suggestions that involve > -force. I suspect there are better ways of working that

Re: Issues with oudated ports / GitHub

On 2016-10-07 19:07, Marcel Bischoff wrote: > On 16/10/07, Ryan Schmidt wrote: >> The problem is: somebody needs to do the correct work to update each of >> those ports to the latest version. In many cases, tickets are already >> filed, and you can look them up to see what the current status is;

Re: Working with Git

> On Oct 7, 2016, at 6:56 PM, Rainer Müller wrote: > > If you want to replace the commits in a pull request, it will require a > 'git push --force' to the branch of the pull request. I think this would be fine, since only a few people are likely to fetch a pull request

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 4:02 PM, Rainer Müller wrote: > > On 2016-10-07 20:58, Christopher Jones wrote: >> >>> On 7 Oct 2016, at 7:40 pm, Lawrence Velázquez >>> wrote: >>> On Oct 7, 2016, at 2:09 PM, Chris Jones

Re: Issues with oudated ports / GitHub

On 2016-10-07 20:58, Christopher Jones wrote: > >> On 7 Oct 2016, at 7:40 pm, Lawrence Velázquez >> wrote: >> >>> On Oct 7, 2016, at 2:09 PM, Chris Jones >>> wrote: >>> >>> Currently, once they find out about svn, and trac >> >> We will still

tcl question: defining dynamically named variables in a namespace

Hi, I have a procedure in a PortGroup that is used to define dependency variables for KF5, hiding the whole mechanism behind kf5-foo and kf5-foo-devel interchangeability from the casual port developer (and making it easy for myself too). Basically: {{{ proc kf5.framework_dependency {name

Re: tcl question: defining dynamically named variables in a namespace

sorry for the noise, it seems I can simply use namespace upvar kf5 ${name}_dep dep etc. Now, would it be possible and worth the trouble to put kf5.framework_dependency procedure itself into the dedicated namespace? R. ___ macports-dev mailing list

Re: tcl question: defining dynamically named variables in a namespace

It's been a long time I haven't done Tcl development, but from memory: namespace eval { --> your code here <--- } should do what you're trying to do. -- David On Fri, Oct 7, 2016 at 2:12 PM, René J.V. Bertin wrote: > sorry for the noise, it seems I can simply use >

Re: Issues with oudated ports / GitHub

> On Oct 7, 2016, at 3:24 PM, Ken Cunningham > wrote: > >> On 2016-10-07, at 10:05 AM, Rainer Müller wrote: >> >> I am not sure how we could change these to make triaging trickets >> easier. > > I can't easily just look at the list and see what are new