Hi, I am one of the upstream Disco developers.
To clarify, triq is not a strict dependency of Disco. Disco only depends on triq to implement some unit tests for the Erlang code, which are triggered only by the 'make test' target. We build Disco debian packages on machines that do not have triq installed. Secondly, the only binary blob that I can find in the triq source tree is rebar, which is essentially contains the Erlang byte-code for the rebar tool: https://github.com/basho/rebar Hence, this is not a closed-source binary blob, but is buildable from software under the Apache License, version 2.0. This use of a bundled rebar script is fast becoming the standard way of building Erlang projects. Disallowing binary blobs buildable from free software would inconvenience packaging a great many Erlang projects. How do you suggest we proceed? Thanks, --prashanth -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+gqjot27hw0kqfh1s7kevn9sksjw1-yfdcg5uism2ktt+q...@mail.gmail.com
