From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [PROPOSAL] Builder, a build system integration for Emacs Date: Tue, 30 May 2023 17:52:57 -0400 Message-ID: References: <95980ffc-86e7-ad54-4a20-539d8c6ea5d0@mailo.com> <3f68f4bc-d426-0bcc-1329-674c12b29386@mailo.com> <76e12f7c-335f-476b-ffb3-fd8e8e4ab5d0@mailo.com> <87pm6rx4ea.fsf@yahoo.com> <87wn0ytefw.fsf@gmail.com> <83h6s0n95y.fsf@gnu.org> <83edn4myz4.fsf@gnu.org> <83a5xsmuc0.fsf@gnu.org> <3a315ddd3a25a56c8d6a@heytings.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6353"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 30 23:53:16 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q47HH-0001S3-JO for ged-emacs-devel@m.gmane-mx.org; Tue, 30 May 2023 23:53:15 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q47H4-0002S6-W0; Tue, 30 May 2023 17:53:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q47H0-0002Nu-CL for emacs-devel@gnu.org; Tue, 30 May 2023 17:52:58 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q47H0-0003PE-4F; Tue, 30 May 2023 17:52:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=qiCJHrimPpL+Z3bba5vsJNTSh7aKLWvZjh2IWyWLgu0=; b=fMyHOVF0ofz9 u5KdcagsyV4qR9ETCsdLjSaabG6q8rZUs8LbNe+YLRSuNnIiSkJkMmzOYwTrklcLvL3REm38w5h+8 jIumcI05oEGNb+e4+zI/+BPqkM3DcNb4usWrb156icBompWC8v2pFE7RFVIwjjyCHtVpUHP3CvRML sM3NBVDP7ZFxuxvzi299aPp7z/RNXhVCa2x7lH6vgEVwHdTIzwXmW63oXj9WGJQdmbO4I5epkLI5M NdyDnNtYD7xsR5IuL0Vqbtg2zX93Mje3Gkfx5ArGKxFVEPIjvBhMyvOeKFRxK4ZQBO51ucFgjLCM0 5NyfkDbJKvxkQ1ZVQEzfCg==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1q47Gz-0003il-L4; Tue, 30 May 2023 17:52:57 -0400 In-Reply-To: (message from Gregory Heytings on Mon, 29 May 2023 22:05:29 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306429 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > 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), It is useful that that feature exists, but it can't by itself correct this problem. The problem is that cargo will link programs with nonfree libraries if they specify those libraries. A free distro must not _by default_ offer any nonfree libraries for linking. If a user requests explicitly to link with specified nonfree modules, the linker will do it, but a free distro never does that _on its own initiative_ or suggests doing that. -f would help a person building a Rust program find out whether it would use any nonfree libraries, but (1) searching its output for all the nonfree licenses could take some time and knowledge, and (2) not all users will bother to check that. 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). It may be able to do the job with this feature. But we might want to modify Cargo so that it blocks those licenses unconditionally. Also, do Rust users make a habit of looking at the list of packages in crates.io in other ways? Either thru features of Cargo, or directly thru various network protocols? > > I think we should move this to gnu-prog-disc. It is simply that this issue is not really on topic for emacs-devel. I feel we should save it for discussion of developing GNU Emacs. > I'm not subscribed to that mailing list, which AFAIK is an internal > mailing list with restricted access. It is meant for people participating in developing GNU. Are you working on developing GNU Emacs? If so, that includes you. Or I can cc you in the messages of this discussion and ask others to do likewise. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)