From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Merging bignum to master Date: Mon, 13 Aug 2018 19:31:11 -0400 Message-ID: References: <877ekwu1mn.fsf@tromey.com> <48742e8c-fffb-7fe0-bb12-2ce3dc171603@cs.ucla.edu> <837ekvlau2.fsf@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: blaine.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: blaine.gmane.org 1534203031 30507 195.159.176.226 (13 Aug 2018 23:30:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 13 Aug 2018 23:30:31 +0000 (UTC) Cc: eliz@gnu.org, ulm@gentoo.org, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 14 01:30:27 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fpMI6-0007qz-HF for ged-emacs-devel@m.gmane.org; Tue, 14 Aug 2018 01:30:26 +0200 Original-Received: from localhost ([::1]:41793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fpMKC-0001Qm-W3 for ged-emacs-devel@m.gmane.org; Mon, 13 Aug 2018 19:32:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38576) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fpMIz-0001D0-KF for emacs-devel@gnu.org; Mon, 13 Aug 2018 19:31:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fpMIy-0000Jj-Ni for emacs-devel@gnu.org; Mon, 13 Aug 2018 19:31:21 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:33514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fpMIq-0000Er-2x; Mon, 13 Aug 2018 19:31:12 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1fpMIp-0003m9-JR; Mon, 13 Aug 2018 19:31:11 -0400 In-Reply-To: (message from Paul Eggert on Sun, 12 Aug 2018 16:53:07 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228508 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. ]]] Eli said: > The autoconf manual says about --enable: "They should only cause parts > of the program to be built rather than left out." Yes, but that is a superficial way to look at it. The real intended meaning of --enable is to include a feature, or support for some feature. So --enable option ought to be named after the feature it enables, NOT after some piece of code. If we stick to that, the substantial difference between --enable and --with will be clear, so people will not confuse them. > That being said, the distinction between --with-FOO and --enable-FOO has long > been a confusing area of the GNU coding standards -- as witnessed by the other > packages you're thinking about. Is that because some cases have been handled erroneously? Or is it because some cases don't really fit into either --with or --enable? If the latter, I think we need to take the bull by the horns and work out a good way to handle those cases, rather than forcing them into one of two slots which they do not fit. -- Dr Richard Stallman President, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)