Getting the build script to a working state #157
Conversation
incase url's that don't put the file in the url.
working script will; Remove existing folders named in the sources Download the packages listed in sources.json Extracts the above packages deletes the downloaded package
| @@ -12,6 +12,7 @@ | |||
| { | |||
| "name": "conemu-maximus5", | |||
| "version": "140124", | |||
| "url": "http://www.fosshub.com/download/ConEmuPack.140124.7z" | |||
| "url": "http://conemu.codeplex.com/downloads/get/782952", | |||
| "package": "ConEmuPack.140124.7z" | |||
There was a problem hiding this comment.
Can we somehow avoid this? The link I used was nice, but as you changed it I guess b/c it does not allow hot linking.
Could we possibly just name the download the archive, name it conemu-maximus5.zip (or just conemu-maximus5). I am pretty sure 7z only cares about archive metadata/headers. That way we can avoid caring about the extension and filename and this field will be unnecessary.
There was a problem hiding this comment.
Yeah without hotlinking it's fairly useless.
You can name that package key whatever you want if you set it, otherwise the script pulls the name and url extension together sets that as the package, and carries on.
|
Very good work. I did not know that about the majority of the stuff :-D so good thing you checked it out. |
Getting the build script to a working state
I didn't mean to re-write as much as I did. It was mostly working as it was but I kept on going to handle some edge cases.
I think because I used
invoke-webrequestthis is not PSv3.0 only. I'll come back to looking at this to use the .NET Webclient. I was trying to get it to run in parallel.If you run
in powershell you'll see why the top comment is so funky and why using types helps.
Could could still do with handling being executed outside the the cmder/scripts directory. And a swath of other things.