Ravenports / ravenadm

Administration tool for Ravenports
http://www.ravenports.com
ISC License
17 stars 3 forks source link

more verbose ( debug? ) output into the build logs #19

Closed magenbluten closed 4 years ago

magenbluten commented 4 years ago

while working ( at least trying to ) on ravensw i noticed that the actual configure and make commands are not logged:

[snip]
--------------------------------------------------------------------------------
--  Phase: configure
--------------------------------------------------------------------------------
===>  Configuring for ravensw-standard
No installed jimsh or tclsh, building local bootstrap jimsh0
[snip]

it would be helpful to see the actual full configuration command.

e.g:

[snip]
--------------------------------------------------------------------------------
--  Phase: configure
--------------------------------------------------------------------------------
===>  Configuring for ravensw-standard
=> executing: `./configure --pkgconfigdir=/raven/lib/pkgconfig/ --prefix=/raven`
No installed jimsh or tclsh, building local bootstrap jimsh0
[snip]

i would be helpful to have this for:

kraileth commented 4 years ago

I've had cases like this before, too, where I ended up reconstructing the actual command myself (from the *_ARGS etc). Would be rather helpful to just have the exact command in the log.

jrmarino commented 4 years ago

this is actually not a ravenadm issue, but a framework issue (ravensource)

jrmarino commented 4 years ago

the next release will have a verbose configure stage where you can see the command

jrmarino commented 4 years ago

The "extract" and "patch" phases are already pretty well logged but perhaps the "build" phase could be logged better (similar to configure is now)

jrmarino commented 4 years ago

Alright, I've exposed the environment and the build command to the logs on the default "do-build" target.
It will be available on next release. I think we can close this issue as it's been addressed.