search

Badgerati / Fudge

Fudge is a PowerShell tool to help manage software packages via Chocolatey for specific development projects. Think NPM and Bower, but for Chocolatey
MIT License
21 stars 3 forks source link

Verbose mode #46

Open jayvdb opened 5 years ago

jayvdb commented 5 years ago

It would be helpful to have a verbose mode, especially to show what was hidden during Format-ChocolateyList, and this should be default if there was an error during a chocolatey action.

I am guessing I can do something like

fudge install;
cat C:\ProgramData\chocolatey\logs\chocolatey.log;

But that is a bit clumsy.

jayvdb commented 5 years ago

I didnt find a suitable workaround for this, so this is probably the most critical problem with adopting Fudge -- the choco logs are quite important for a few reasons. Capturing the choco log for each Fudge item, and storing it in accessible place will allow inspection of the choco logs in the post install or afterwards.

Maybe each of the "i want to see the choco log" reasons is worth exploring and solving separately.

One is "I unexpectedly have 5 new packages which are dependencies of the Fudge items, and I want to know which Fudge item caused it". Yes, I can find that by going to chocolatey.org for each of the packages, but that gets annoying as the list of Fudge items grows. A "fudge tree" instead of "choco list" would be helpful ;-)

Badgerati commented 5 years ago

I love the idea of a fudge tree! It would require storing a known state of packages for Fudge, perhaps in APPDATA - which could also be somewhere to store the choco logs (and other logs for other providers). A fudge logs could open the directory?