Re: [PROPOSAL] Builder, a build system integration for Emacs

[Gregory Heytings]

> > There are at least two options to do that, which were already mentioned 
> > upthread: (1) running "cargo tree -f '{l}'", which will display the 
> > license of each of the dependencies of the program, recursively (that 
> > option works out of the box), and (2) installing a plugin for cargo, 
> > named "cargo deny", which is itself free software, and with which you 
> > can check, again recursively, whether all the dependencies of a program 
> > are free (more precisely: have a license that is present in the list of 
> > licenses you have chosen to allow).
>
> Since that plug in is not included in a default installation of Cargo,

Typing "cargo install cargo-deny" is all you need to install it.

Designers of a language cannot force all users of that language to make 
their software free.  They can incite them to do so, and can provide them 
with tools to do so.

> it is still unacceptable.

What makes you believe that you can decide what is acceptable and what is 
not?  Richard is asking for facts, your categorical judgements are out of 
place here.

> And displaying each license of each package in a deep dependency tree 
> counts as ``studying'' in my book.

I was replying to Richard, who said "It means that any time you build a 
Rust program that you have not thoroughly studied, you don't know whether 
it will incorporate nonfree software."  Displaying a list of licenses and 
checking that it doesn't contain any non-kosher ones is evidently not 
"thoroughly studying" a program.  And you can even create a short shell 
script to simplify your task, something like:

cargo tree -f '{p}: {l}' | sed 's/^[^a-z0-9]*//' | sort | uniq | grep -Ev 
'\(\*\)$|^build-dependencies] *$|MIT|Apache-2.0|GPL|BSD|ISC|MPL|Zlib'