Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>

Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Gregory Becker <[email protected]>

Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Gregory Becker <[email protected]>

Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Gregory Becker <[email protected]>

Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Gregory Becker <[email protected]>

Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Gregory Becker <[email protected]>

Logging in the new installer was modeled after the old installer, but it has
proven to be problematic as it requires the stage dir to exist before a log
file is created:

1. many things can go wrong before the stage dir is created
2. for build cache installs pkg.stage is obviously not used, but we do
   need a log file to troubleshoot failures. In the old installer this was
   no issue, because install from binary cache was done sequentially
   from the main process
3. there is output *before* creating the stage dir that needs to be silenced to
   not mess up the UI

This commit generates a unique log file in the stage dir root, redirects output
to that as early as possible, and then ultimately symlinks the log file
in the package stage dir in the usual location during source builds.

Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Gregory Becker <[email protected]>