Issue 106296 - store external tarball outside scm (build env. changes)
Summary: store external tarball outside scm (build env. changes)
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: solenv (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: hjs
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks: 106731
  Show dependency tree
 
Reported: 2009-10-26 16:27 UTC by hjs
Modified: 2013-08-07 15:34 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hjs 2009-10-26 16:27:59 UTC 
currently external source tarballs are hosted in the modules where they are
built. the drawback is that these files are binary blobs that add their size to
the repository each time an update is done.
while it makes sense to have the patches, makefiles and similar in the scm, it
might be an option to move the tarballs out of the repository and have them
prefetched somewhere else.
Comment 1 hjs 2009-11-09 13:13:10 UTC 
external code modules now fetch their tarballs from TARFILE_LOCATION if set.

see also follow up issue #i106296#
Comment 2 Mathias_Bauer 2009-11-11 09:20:05 UTC 
looks good
Comment 3 hjs 2009-11-17 10:05:30 UTC 
.