emrge --info got longer over the time. Many users cannot paste it anymore: "Comments cannot be longer than 16384 characters. If you need to post contents of files or logs, use the attachment feature instead." We should select one of the following options: 1) shorten emerge --info 2) allow longer texts 3) add a dedicated text field with a different limit 4) ask to *attach* the emerge --info instead of pasting it Reproducible: Always
We could also include it automatically in build logs.
(In reply to Michał Górny from comment #1) > We could also include it automatically in build logs. The most important information of build.log is at their beginning and their end, so I don't think it would be a good idea to obstruct them by prepending or appending emerge --info output.
Yet ago is doing that anyway, so that battle's lost by now. I suppose the info at the beginning is roughly a subset of 'emerge --info', so I suppose we could place it after the initial bits and before first phase function output. However, it should probably be printed only to build log and not to console.
