From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Supporting multiline Package-Requires header Date: Tue, 11 Aug 2015 10:28:16 +0100 Message-ID: References: <877fp3dxt2.fsf@gmail.com> <8737zrcft1.fsf@members.fsf.org> <87k2t2b4fd.fsf@members.fsf.org> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1439285314 6458 80.91.229.3 (11 Aug 2015 09:28:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 11 Aug 2015 09:28:34 +0000 (UTC) Cc: emacs-devel To: Nicolas Richard Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 11 11:28:34 2015 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 1ZP5rF-0000UJ-T3 for ged-emacs-devel@m.gmane.org; Tue, 11 Aug 2015 11:28:34 +0200 Original-Received: from localhost ([::1]:33509 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZP5rF-0005TF-Dd for ged-emacs-devel@m.gmane.org; Tue, 11 Aug 2015 05:28:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZP5r3-0005St-Pp for emacs-devel@gnu.org; Tue, 11 Aug 2015 05:28:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZP5r0-0005XG-O4 for emacs-devel@gnu.org; Tue, 11 Aug 2015 05:28:21 -0400 Original-Received: from mail-lb0-x236.google.com ([2a00:1450:4010:c04::236]:33439) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZP5r0-0005Wm-D2 for emacs-devel@gnu.org; Tue, 11 Aug 2015 05:28:18 -0400 Original-Received: by lbbsx3 with SMTP id sx3so26076249lbb.0 for ; Tue, 11 Aug 2015 02:28:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=axT1T3XC5Bwx8m/OAjfilCUj6qGMeEhhwQ/2dsyhxNs=; b=EWu32yFeUVAzaRBdm9CAYTer1YV6qreqsx2pxRMwUEcinyJ5ZbgDs5DWyUl+vw/LVU sl1RIe9adsfCPwSh/Khjn3I6+p/WlianMA9oc/pc9fl2sbVZI4lIdT0xeohNXoDP4lha /4gTM2D+JdQSJ37u0YjI79QtirHrjP8fkRjzK8oQK6bP8BPpY0jmKacthMLwLGZkUseC am6Sy6977QryIfqQiiKscf/0akferdF0Vlnswyr09G6EfmDqHNPFwArn8CSni5CTjXaO qWMEWJ7WCGDuA6pZDVPfOGx2W9SjY7TDxGlC8tU7/o3VdM8R7kA9h+Wj7Qs0/9IZAPfT uUqA== X-Received: by 10.112.210.137 with SMTP id mu9mr24615371lbc.95.1439285297018; Tue, 11 Aug 2015 02:28:17 -0700 (PDT) Original-Received: by 10.25.134.139 with HTTP; Tue, 11 Aug 2015 02:28:16 -0700 (PDT) In-Reply-To: <87k2t2b4fd.fsf@members.fsf.org> X-Google-Sender-Auth: YMvyOl49ic4OC-XOQg3njPRC_oo X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::236 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:188720 Archived-At: 2015-08-11 9:44 GMT+01:00 Nicolas Richard : >>> I understand that the new tools will work with old files, but will the >>> new files work with the old tools ? i.e. will it be possible to install >>> these packages to emacs 24.5 ? >> >> No. A package that writes it like this will only be (properly) installable on Emacs 25 and up. >> >> Of course I'd never drop support for Emacs 24 on one of my packages >> just for the sake of this minor feature. But once I start routinely >> requiring Emacs 25.1 because of other features, I'll be glad to have >> this as a bonus. > > It makes sense. My worry is also that emacs-24 must have a way to > understand that the package is "not installable". e.g. we don't want > list-packages to suddenly break on older emacsen (I have no idea if this > can actually happen). I don't think this can happen. `list-packages' receives information from the archives, it doesn't manually parse remote packages (it parses already-installed packages, but if it has been installed already then it must be compatible). As long as the archive servers are using the latest Emacs release, they'll know that the package requires Emacs 25, and they'll provide that information to the user during `list-packages'. (And besides, even if the archive is using Emacs 24, or if the user tries to manually install the package, they'll be immediately greeted with an error, telling them something is wrong.)