Opened 8 years ago
Last modified 8 years ago
#52973 new enhancement
add setting to allow main.log truncation
Reported by: | RJVB (René Bertin) | Owned by: | |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | base | Version: | |
Keywords: | Cc: | jmroot (Joshua Root), mkae (Marko Käning), kurthindenburg (Kurt Hindenburg) | |
Port: |
Description
Hi,
Looking at the changes in master/head I noticed commit 0be55cb9 from March 16th 2016 which changed logfile truncation to appending.
I can imagine how this would be of interest for some forms of port maintenance, but I see 2 main reasons why the previous truncation approach was better:
- hunting down build errors from a trac report is usually easier if one can request the reporter to do a 2nd
port build
orport destroot
run and upload the shorter logfile too. This is all the more true when the log is made on a recent Mac that has 8 cores or even more.
- logfiles can grow significantly if one does incremental builds during (-devel) port development without frequent
port clean
s.
Ideally truncation/append would be controlled by a setting in macports.conf that determines the default, with a possibility to override that default on the commandline.
Change History (6)
comment:1 Changed 8 years ago by larryv (Lawrence Velázquez)
Priority: | Normal → Low |
---|---|
Summary: | main.log truncation option → add setting to allow main.log truncation |
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
comment:3 Changed 8 years ago by mkae (Marko Käning)
Cc: | mkae added |
---|
comment:4 follow-up: 5 Changed 8 years ago by RJVB (René Bertin)
Please note that I mentioned the short log as a 2nd attachment.
comment:5 Changed 8 years ago by larryv (Lawrence Velázquez)
There is no reason to ask for a second attachment that by definition contains less information than the first one.
comment:6 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Cc: | kurthindenburg added |
---|
I find this change to be annoying as well - it just causes you to have to remember to do a 'port clean' to avoid previous errors in the log
Replying to RJVB:
We do the opposite: If a user has submitted a bug report with a truncated log, we ask them to redo the build from scratch and attach the full log. It's the first thing mentioned in the bug reporting instructions.