Regarding my last statement: It would make the bootstrapping script resistant to download interruptions, because the same curl command would finish the download when repeated. ` I mean returning the HTTP 416 for resumes of completed files would make the same curl -C - ... to return success in every three cases: when download of the file hadn't been started yes and it finishes. when the file to download is incomplete and the download finishes. when the file to download is already complete. ` Now the...
Regarding my last statement: It would make the bootstrapping script resistant to download interruptions, because the same curl command would finish the download when repeated. ` I mean returning the HTTP 416 would make the same curl -C - ... to return success in every three cases: when download of the file hadn't been started yes and it finishes. when the file to download is incomplete and the download finishes. when the file to download is already complete. ` Now the 3rd case returns exit code 33...
Regarding my last statement: It would make the bootstrapping script resistant to download interruptions, because the same curl command would finish the download when repeated. I mean returning the HTTP 416 would make the same curl -C - ... to return success in every three cases: when download of the file hadn't been started yes and it finishes. when the file to download is incomplete and the download finishes. when the file to download is already complete. Now the 3rd case returns exit code 33 which...
Regarding my last statement: It would make the bootstrapping script resistant to download interruptions, because the same curl command would finish the download when repeated. I mean returning the HTTP 416 would make the same curl -C - ... to return success in every three cases: when download of the file hadn't been started yes and it finishes. when the file to download is incomplete and the download finishes. when the file to download is already complete. Now the 3rd case returns exit code 33 which...
Resuming a finished http download wrongly return `HTTP 302`+`HTTP 200´ instead of the expected `HTTP 416`
Hello. A couple of questions: I read OviOS uses pacman for package management, but otherwise is unrelated to Arch Linux. What other distros inspired OviOS / had useful software that you reused here? How many developers are working on OviOS at the moment?
(EDIT: Just synced the source code, hence fixing my reply) Thanks for adding the change. I would capitalize it as "Developer build", though. I would also like this to stand out of the whole list more. Maybe move it to the top of this list? Also "SCM checkout" phrase doesn't catch my attention in the right way. Something more specific would be appreciated, like "Daily snapshot" or "Development version". Thanks in advance.
(EDIT: Just synced the source code, hence fixing my reply) Thanks for adding the change. I would capitalize it as "Developer build", though. I would also like this to stand out of the whole list more. Maybe move it to the top of this list? Also "SCM checkout" phrase doesn't catch my attention in the right way. Something more specific would be appreciated, like "Daily snapshot" or "Development version".