Justin thanks for the input. For context, Superset ships as a Python [Flask] backend and a Javascript frontend web app. Currently we distribute a package on Pypi that contains minified Javascript bundles. The product can't really work do much without the Javascript, only the "data access layer" works, but that's a very small portion of what Superset has to offer.
>From my understanding we can't really ship just our code or binaries and have people fetch the rest of the deps and build/install it, can we? If that was the case, the Superset Apache release could really just be a tarball with source and and an installation script that would fetch all the deps and build the JS. Would that work? Max On Tue, Sep 4, 2018 at 2:01 PM Justin Mclean <[email protected]> wrote: > Hi, > > > I started doing some work towards building a LICENSE.txt dynamically > > out of NPM and Pypi metadata. Superset's dependency tree is huge. It > looks > > like this may need a fair amount of investigation and perhaps revising > some > > dependencies that we can't have, or making some deps optional. > > Remember it's not dependancies that are mentioned in LICENSE only what is > bundled within the release, I notice some build tool and the like in that > list that probably don't need to be mentioned. [1] Note as well that the > LICENSE may be different for the source release and the convenience binary > release. > > Thanks, > Justin > > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
