Hello,
On Wed, 6 Feb 2013 14:30:37 -0600 Zach Pfeffer zach.pfeffer@linaro.org wrote:
[]
ACCEPT_LICENSE=<license_id>
Where <license_id> is id under which license is registered in linaro-license-protection. One good way to figure it out is to read the license page at all (well, as HTML source, the id is included in some links). Wording of variable name (as well as of commands in underlying implementation) is also explicit to point that its usage construes license acceptance.
Paul, can you list the links you're looking at?
Yes, sorry, just didn't want to overload initial mail with info. Suppose, we want to add file from this dir as SOURCE_OVERLAY: http://snapshots.linaro.org/android/binaries/origen/20121220/ . Clicking on the file in clean browser session, we get license acceptance page, and Ctrl+U'ing it, at the bottom, where HTML corresponding to buttons is, we see:
<form action="/accept-license?lic=9fa99e541b3b291f0ba460104b354d0c&url=android/binaries/origen/20121220/vendor.tar.bz2" method="post">
"9fa99e541b3b291f0ba460104b354d0c" is the hash id for this particular license, so build config needs include
SOURCE_OVERLAY=origen/20121220/vendor.tar.bz2 ACCEPT_LICENSE=9fa99e541b3b291f0ba460104b354d0c
I prototypes these changes using https://android-build.linaro.org/builds/~pfalcon/panda-jb-gcc47-tilt-trackin... which is down to 2h10m build time. I'm ready to migrate all builds tomorrow, while we're early in cycle start.
Please let me know if there're any issues with approach or proposed migration timeframe, otherwise let's make android-build rock again.
I really like the fact that you've shaved an hour off the build.
One thing I'm curious about, why does this work? It seems like licensing issues and autobuild issues should be separate concerns.
Yep, it's just switching autobuild from using sluggish layers of proxies to fast direct downloads calls for need to deal with licensing.
Another thing. What about support for an upcoming use case where we're need multiple EULAs. Would you use a comma separated list in the define?
Yes, I thought we didn't use multiply licensed overlays, but if we will, ACCEPT_LICENSE can take comma or semicolon separated list, just as SOURCE_OVERLAY does.