Prepare mirror tarball for 3rd party dependencies

Bug #801530 reported by Paul Sokolovsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android Frontend
Won't Fix
Low
Unassigned

Bug Description

This is offshot of WI "Improve frontend installation (external dependencies)" of https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-buildd-deployment

Install script pulls a bunch of 3rd party components from the net. Non-availability of any of them means installation failure. We sure insure against prolonged non-availability. Within scope of BP above it was discussed what approach is good, and we seem to agree that good way is to prepare tarball of all 3rd party dependencies and put somewhere. Then, provide wrappers for common net access tools like wget, which will try to use upstream servers, and if fail, then take component from mirror tarball.

This is not high-priority, as we use official download locs, and for 50+ times I ran deployment script, I never had network failure.

Changed in linaro-android-build-tools:
importance: Undecided → Low
status: New → Triaged
affects: linaro-android-build-tools → linaro-android-frontend
Revision history for this message
Alan Bennett (akbennett) wrote :

Due to the age of this issue, we are acknowledging that this issue will likely not be fixed. If this issue is still important, please add details and re open the issue.

Changed in linaro-android-frontend:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.