tw_cli-10.2 -> tw_cli-10.2.2.1 version bump Reproducible: Always
Created attachment 348540 [details] Updated tw_cli ebuild
Created attachment 348542 [details] Updated tw_cli ebuild (revised) Remove the wget lines for fetching without the EULA, it shouldn't be included in the distributed ebuild for legal reasons.
This should also resolve #432140
Created attachment 348544 [details] Corrected ebuild I appear to have mixed up the relationship between QA_PRESTRIPPED and QA_PREBUILT. QA_PREBUILT implies QA_PRESTRIPPED, not the other way around, ebuild updated accordingly.
I have an ebuild ready to go, I'm just talking to the licenses team about the LSI license, because the EULA presented is very different than the existing LSI license in the tree. Specifically, I think we CAN redistribute: The clickthrough presented is here: http://www.lsi.com/Pages/user/eula.aspx There are two blocks in the EULA of specific interest: ===== 2. Grant of Rights 2.1 LSI Binary Code. Subject to the terms of this Agreement, LSI grants to Licensee a non-exclusive, world-wide, revocable (for breach in accordance with Section 7), non-transferable limited license, without the right to sublicense except as expressly provided herein, solely to: (c) Distribute the LSI Binary Code as incorporated in Licensee's Products or for use with LSI Devices to its Subsequent Users; (d) Distribute the Explanatory Materials related to LSI Binary Code only for use with LSI Devices; 3. License Restrictions 3.1. LSI Binary Code. The Licenses granted in Section 2.1 for LSI Binary Code and related Explanatory Materials are subject to the following restrictions: (a) Licensee shall not use the LSI Binary Code and related Explanatory Materials for any purpose other than as expressly provided in Article 2; (b) Licensee shall reproduce all copyright notices and other proprietary markings or legends contained within or on the LSI Binary Code and related Explanatory Materials on any copies it makes; and ===== So from this, we CAN distribute it ourselves per 2.1.c, as long as we include this EULA with it per 3.1.b.
InCVS, thanks for the submission.
