You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
what do you think about excluding uses-nonfree too, because i think it's only used when:
some (potentially optional) dependencies are nonfree, which would already turn up in our list
it is referring to, linking to, or endorsing problematic packages
it integrates with problematic packages (can still be free!)
take mesa for example, the "issues" parabola identified are that it's recommending optional problematic software, but on its own mesa is licensed under MIT
The text was updated successfully, but these errors were encountered:
My take: I don't know.. It really depends on the definition. We could do it but then we would steer away from the FSF definition. I'm interested to hear more opinions.
From @coderobe :
what do you think about excluding
uses-nonfree
too, because i think it's only used when:take
mesa
for example, the "issues" parabola identified are that it's recommending optional problematic software, but on its ownmesa
is licensed under MITThe text was updated successfully, but these errors were encountered: