-
-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the mingw setup script log to a file #49
Comments
There is a good solution for this, and is actually quite easy (but maybe not exactly prefered). .\setup.ps1 | Tee-Object -FilePath output.txt Has the desired result (It outputs every single line to the console, as well to the output.txt file). A very similar thing can be used for the linux version of the script (but maybe there is a better solution to this) This, however, means that there needs to be an extra file, which could be confusing |
I don't think the extra file thing is an issue. I'll try your solution now! EDIT: Works great :) |
After writing a 50 lines comment, Firefox crashed and all the comment was deleted. Great. Sorry if this comment lacks too much detail. If we go with this solution, we will need to decide a few things:
My suggestions:
I'm going to see how can the same be done for the .sh file, but if i recall correctly, a very similar solution can be obtained with even simpler code. Edit: Is the exact same for the sh script. We still need to decide where between the different options i listed beore |
setup-no-log.ps1 would be fine i think, not too important.
This depends on how exactly nimbal wants the debugging information but i honestly think a single overwriting setup-output.txt file would be enough! :) |
Ok, i'm going to make the changes and hopefully remember how to make a pull request. This, however, might conflict with other branches as the setup.ps1 file will now be completelly diferent, and other branches that are based on the current setup that modify that file will need to be changed manually (and by that i mean the sound branch) Edit: I'll make the new files be called setup-logged.ps1 That prevents the conflicting branches and is easy to change anyway afterwards. Edit2: Oops, i believe i just pushed the changes. But creating a whole new branch for that seemed unnecesary, and it seems that i cannot create a pull request directly from my computer |
Yeah there'll have to be some merging action, but nothing too troublesome i imagine! |
For troubleshooting, it would be very helpful to log the output of the setup script to a file that users can upload for diagnostics.
The
start-transcript
andstop-transcript
cmdlets may be useful for this, but they have problems as detailed in this bug report. One of the workarounds listed there might be interesting.The text was updated successfully, but these errors were encountered: