From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.devel Subject: Re: Tests, Emacs-25 and Conditional Features Date: Fri, 18 Mar 2016 17:22:24 +0000 Message-ID: <87mvpvem5r.fsf@russet.org.uk> References: <87k2l2zgre.fsf@russet.org.uk> <87h9g6xzrb.fsf@gmx.de> <87shzpxvfv.fsf@russet.org.uk> <83y49f94kt.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1458321844 6443 80.91.229.3 (18 Mar 2016 17:24:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 18 Mar 2016 17:24:04 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 18 18:23:48 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1agy7V-00087d-O1 for ged-emacs-devel@m.gmane.org; Fri, 18 Mar 2016 18:23:29 +0100 Original-Received: from localhost ([::1]:45244 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agy7V-0000XN-3K for ged-emacs-devel@m.gmane.org; Fri, 18 Mar 2016 13:23:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agy6e-0007Sg-MB for emacs-devel@gnu.org; Fri, 18 Mar 2016 13:22:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1agy6a-0005yb-Hm for emacs-devel@gnu.org; Fri, 18 Mar 2016 13:22:36 -0400 Original-Received: from cloud103.planethippo.com ([31.216.48.48]:51413) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agy6Y-0005xo-PX; Fri, 18 Mar 2016 13:22:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From; bh=IF8cWAyqePwI8HUJMEawgMrXeZwhxJ+wadHfv4/2gv0=; b=MLJRwgsLEw6bGn+5FqHMmNJVGj jpVeWk6I+A4lDDSwAvrH1TpzbyMtxHuXjzW9r9w5RwFe82vmuYFJeUcWN6mzTtzo8u8wEEG5LvH7B awGsVuHPlg5m2UjaDDgJ9zhGQrFmfB6SXG1ZHRrNO0BUW/w0CwEAsEYm4owvYZv00optNjqtPa4Bb n+LblnpU2KrILG0PMUJ7HSMVHCM6hh2J6aenp6TxJBIgJRz9vZUffliW3tMf7Ev48EfHMbZi2Ijzr SP0ChY7DY2gVS+U5qiRsIBWyWaQeNt93cSxvkfFjGWy21OvA9s42+9w8vfl1+P2z6rWEmrl7qBK8g XndtdSNg==; Original-Received: from janus-nat-128-240-225-60.ncl.ac.uk ([128.240.225.60]:59948 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86_1) (envelope-from ) id 1agy6X-002HaM-LR; Fri, 18 Mar 2016 17:22:29 +0000 In-Reply-To: <83y49f94kt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 18 Mar 2016 17:41:06 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 31.216.48.48 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:201835 Archived-At: Eli Zaretskii writes: >> From: Stefan Monnier >> Date: Fri, 18 Mar 2016 11:15:59 -0400 >> >> > Yeah, thought about that. But then the test is skipped if >> > gnutls-available-p returns nil. What happens if I believe that I have >> > configured and build Emacs to include gnutls, but, for some reason it >> > isn't. The test will be skipped when it should succeed. >> >> This probably calls for a different kind of test. >> E.g. one that takes the system-configuration-options and then confirms >> that the build has the corresponding features. > > That's one possibility, but it isn't the only one. Some of the > features in system-configuration-options are detected automatically, > so the user might not always be aware that a feature she assumed she > has failed to auto-detect and is disabled. > > Maybe a test that produced a report for which features are actually > available and working would be a possible solution. Failing a test, even a GUI which says "I have these features" would be nice. I can add that. Phil