livecheck and distfiles overwrite main.log

[ryandesign (Ryan Carsten Schmidt)]

"port livecheck foo" overwrites port foo's main.log file. This is unexpected.

Even more unexpected was when I ran "port livecheck foo" while "port build foo" was running in another terminal window. (It was taking awhile, and I wanted to make sure I wasn't wasting time building an old version.) This resulted in a main.log file that contained the livecheck debug output, followed by lots of null bytes, followed by a portion of the build log.

It would be great if livecheck would not write to the main.log file.

[ryandesign (Ryan Carsten Schmidt)]

Same with "port distfiles foo"

[larryv (Lawrence Velázquez)]

Cc Me!

[jmroot (Joshua Root)]

This should no longer be the case in current master since logs are appended to now, right?

[raimue (Rainer Müller)]

Even then the livecheck log messages will probably be somewhere between the build log messages. Writing logs is not possible if run without sudo, while the command itself works just fine this way, so logs will already only be written in some cases.

Is there a reason to ever write logs for these port targets? I think logging should honor target_state ${org.macports.livecheck} no, which is also used on other targets and for example also prevents creating a work directory.