Hi,
On Fri, Jan 12, 2018 at 02:42:06PM +0100, db wrote:
> I gave it a try just to see where it would stop or what clues would I
> get in the logs and it didn't even extract, although from a glimpse
> into porttrace.tcl the program used (AFAIR) should have been in the
> allowed system directories.
On 8 Jan 2018, at 21:27, Clemens Lang wrote:
> Note that some ports (e.g. Go) do not build in trace mode, though.
I gave it a try just to see where it would stop or what clues would I get in
the logs and it didn't even extract, although from a glimpse into porttrace.tcl
the program used (AFAIR)
On 9 Jan 2018, at 08:52, Joshua Root wrote:
> 'porttrace yes' in macports.conf should do it. Note that then there's no way
> to turn it off from the command line.
Can not all ports be built in trace mode? Clemens mentioned go.
Do you have any numbers for the performance penalty using port with
> I couldn't find this neither on port's manpage nor in macports.conf.
>
> Is there an option to set trace mode by default?
'porttrace yes' in macports.conf should do it. Note that then there's no
way to turn it off from the command line.
- Josh
Hi,
On Mon, Jan 08, 2018 at 11:17:23AM +0100, db wrote:
> I couldn't find this neither on port's manpage nor in macports.conf.
>
> Is there an option to set trace mode by default?
No, not at the moment. You could contribute an option to do that, if you
want. Note that some ports (e.g. Go) do not
