Opened 7 years ago

Last modified 4 years ago

#41722 new defect

livecheck and distfiles overwrite main.log

Reported by: ryandesign (Ryan Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone: MacPorts Future
Component: base Version: 2.2.99
Keywords: Cc: larryv (Lawrence Velázquez)


"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.

Change History (4)

comment:1 Changed 7 years ago by ryandesign (Ryan Schmidt)

Summary: livecheck overwrites main.loglivecheck and distfiles overwrite main.log

Same with "port distfiles foo"

comment:2 Changed 7 years ago by larryv (Lawrence Velázquez)

Cc: larryv@… added

Cc Me!

comment:3 Changed 4 years ago by jmroot (Joshua Root)

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

comment:4 Changed 4 years ago by 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.

Note: See TracTickets for help on using tickets.