Re: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Monday December 12 2016 00:26:05 Marko Käning wrote: > Given the fact that “port lint" didn’t spot the missing "port:” in front of > the qt5-qtsvg: > --- > -depends_lib-append qt5-qtsvg > +depends_lib-append port:qt5-qtsvg > --- > one might think that “port

Re: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On 12 Dec 2016, at 00:20 , Marko Käning wrote: > Buildbots are finally picking it all up. :) So, now only 10.6-10.8 fail completely (which had to be expected, I am afraid) but qtcurve-gtk2 fails also for the newer ones… Good night, Marko

Re: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On 12 Dec 2016, at 00:03 , René J.V. Bertin wrote: > and lint finds no errors in my local copy Given the fact that “port lint" didn’t spot the missing "port:” in front of the qt5-qtsvg: --- -depends_lib-append qt5-qtsvg +depends_lib-append

Re: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

Turns out that the depspec had to be mended for depends_lib-append… Fixed now. Buildbots are finally picking it all up. :)

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 08:14:13PM +0100, René J.V. Bertin wrote: > > > Just as machine readable as this line. > > > > Wrong, since 'port -q info --line --$fieldname' by definition only > > contains information on $fieldname, whereas your message contains > > natural language. > > Clutching at

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sunday December 11 2016 19:17:13 Clemens Lang wrote: >> Just as machine readable as this line. > >Wrong, since 'port -q info --line --$fieldname' by definition only >contains information on $fieldname, whereas your message contains >natural language. Clutching at straws much? :) Regardless,

Tickets affecting multiple ports and committers & "annoying" commits

Hi, After some cool features have been enabled on Trac, in particular the "See:" and "Closes:" syntax that automatically adds a comment, I wonder what to do with tickets that affect many ports and maintainers. Examples include tickets like "replace no_x11 with x11", "switch to perl5.26", ...

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On 11 December 2016 at 16:53, René J.V. Bertin wrote: > > Let me ask once more: is there anything currently available that makes it > easier/less work to add variants that select a gcc compiler? I've been > looking at the compilers PG, but cannot assess from the preamble comments > whether it's

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sunday December 11 2016 15:59:13 Clemens Lang wrote: > 'port info' output is already parsed by scripts today. It's output is > already machine-readable when using -q info --line --$fieldname. Your > change breaks this. Just as machine readable as this line. This is mostly as a reaction to

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 03:38:14PM +0100, René J.V. Bertin wrote: > > Because it runs 'port -q info --line --subports' and parses the > > result. The flags to info guarantee that only the list of subports > > is printed. > > Portindex? I'm pretty sure I've had a ui_msg for a while in one of my >

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sunday December 11 2016 14:56:23 Clemens Lang wrote: > Two options: > > 1. Modify port(1) to print notes before installation of a port I've volunteered to help find a solution to this situation, but with the underwhelming reception that got I'm not that enchanted to insist. > Because it

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sun, Dec 11, 2016 at 02:28:14PM +0100, René J.V. Bertin wrote: > > A Portfile should not should not print anything in response to it > > simply being opened. (Think about it, does a user really want to see > > this message whenever they run 'port info' > > Yes they are supposed to! Cf. #52981

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On 2016-12-11 23:30 , René J.V. Bertin wrote: On Sunday December 11 2016 12:45:44 Marko Käning wrote: My goodness, what happened here??? That seems to come from this line ui_msg "This port only builds with configure.compiler=macports-gcc-4.7 (from port:gcc47) or newer on OS X

Re: Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

On Sunday December 11 2016 12:45:44 Marko Käning wrote: > My goodness, what happened here??? That seems to come from this line ui_msg "This port only builds with configure.compiler=macports-gcc-4.7 (from port:gcc47) or newer on OS X 10.6" I put that in instead of simply invoking the