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