tanderson69 wrote: ↑
Mon Jan 08, 2018 7:22 pm
I am surprised something like this is allowed by the occt corp. Their repo is only available to signatories of the CLA. I would think exposing a clone to the public would be restricted, but I don't know.
Just prior to the Holidays, I worked with Andrey Betenev, the Opencascade Kernel project manager, to enable the integration of OCCT 7.2 into the Homebrew package manager on macOS. Andrey endorsed source access for this purpose (in fact, Andrey worked internally at Opencascade to fix gitweb access so it returns an identical payload each time it is invoke for sha verification by package managers).
The recently released Homebrew opencascade formula
, uses the gitweb url "http://git.dev.opencascade.org/gitweb/? ... 2_0;sf=tgz
" to download a .tgz of the OCCT 7.2 release. When I asked Andrey to confirm that this access is sanctioned by Opencascade, he responded as follows:
Finally, I want to confirm that this is an approved means for providing Homebrew integration. In other words, we will be in compliance with your licensing terms if we use the gitweb interface to build from sources for the Homebrew formula/distribution.
Using GitWeb to download source snapshots is fully compliant with our rules, and has always been a recommended way to access OCCT for people who needs more than official release but do not have or do not need full access to Git. (The standard way of downloading official version still requires authentication -- we need this to have at least partial statistics on OCCT user base.)
As an aside, Andrey was super responsive and very helpful - a real pleasure to work with him.