From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nicolas Petton Newsgroups: gmane.emacs.devel Subject: Upcoming seq.el version problem with the Emacs release Date: Tue, 16 Feb 2016 14:32:35 +0100 Message-ID: <87vb5osrv0.fsf@petton.fr> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1455629601 25656 80.91.229.3 (16 Feb 2016 13:33:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 16 Feb 2016 13:33:21 +0000 (UTC) To: emacs-devel@gnu.org, Artur Malabarba Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 16 14:33:11 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 1aVfkZ-0005Fa-V8 for ged-emacs-devel@m.gmane.org; Tue, 16 Feb 2016 14:33:08 +0100 Original-Received: from localhost ([::1]:45972 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVfkZ-0002gw-BI for ged-emacs-devel@m.gmane.org; Tue, 16 Feb 2016 08:33:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44525) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVfkA-0002dJ-If for emacs-devel@gnu.org; Tue, 16 Feb 2016 08:32:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVfk7-0007iB-Cm for emacs-devel@gnu.org; Tue, 16 Feb 2016 08:32:42 -0500 Original-Received: from out3-smtp.messagingengine.com ([66.111.4.27]:60100) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVfk7-0007i4-9R for emacs-devel@gnu.org; Tue, 16 Feb 2016 08:32:39 -0500 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 3F5F320ECF for ; Tue, 16 Feb 2016 08:32:37 -0500 (EST) Original-Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 16 Feb 2016 08:32:37 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=SG 9tNc3JxpleU3Svzz+nSSM1/JA=; b=kD+A1JIBE0S99K6/JVrtAjQ06/efFSqhrw EQQh9Q+lTlRF9gARfkBLZjHKf9rA2AWS0wJjFFQlLjXaHqTpC/Sp/fO2e6M6MuKT V26XI6qEIVFDTYiANB87OrqA2AsmdJZiLyY3AkVAZrCc+dPc6cLO/KaNM4JQL4/Z gVbsSDy9w= X-Sasl-enc: ryNEjkU7qooKRKO9pmWJ7VVCZ0ePF0rKLkV5SgTW9+Uj 1455629556 Original-Received: from blueberry (lfbn-1-7726-61.w92-167.abo.wanadoo.fr [92.167.139.61]) by mail.messagingengine.com (Postfix) with ESMTPA id A6F316801DC; Tue, 16 Feb 2016 08:32:36 -0500 (EST) User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/25.1.50.1 (x86_64-unknown-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 66.111.4.27 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:200028 Archived-At: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, We have been discussing with Artur an issue that will appear with seq.el once we'll have Emacs 25.1 out. Quoting Artur: Hi Nico, I just realised a problem that we're about to face. Once Emacs 25 is released,there'll be a version of seq.el (2.x) in the wild, with a fixed set of features. Later on, if you add new features to the seq.el that's on Elpa (whose version is 1.y) these features will be impossible to use without issue. =20=20 For instance, let's say you add seq-map-indexed on version 1.15, and I want to use it on a package. For that, I would require seq.el version 1.15 on my package. =20=20 However, I have no guarantee that I'll get that. If the user is running Emacs 25.1, they'll have a seq.el installed with version 2.something (which satisfies the dependency) but does not contain map indexed. =20=20 The same will happen for all newly added features. And seriously reduces the usefulness of seq as dependency package. One solution would be to have a single seq package on Elpa (carrying a 2.x version number), that offered both implementations. It would have 3 files: =2D seq.el =2D seq-25.el =2D seq-24.el The file seq-24.el would have the exact same contents as the current seq-1.x we have on Elpa except: =2D The file-header and the provide statement would say seq-24 =2D It wouldn't have the package pseudo-headers (no version number, no keywords, etc). The file seq-25.el would have the exact same contents as the current seq-2.x we have in Emacs except: =2D The file-header and the provide statement would say seq-25 =2D It wouldn't have the package pseudo-headers (no version number, no keywords, etc). This way there is only one version of the seq package. Packages that want some recent functionality added in minor-version 12 can simply depend on 2.12, regardless of the Emacs version. Also, packages that want the generics functionality can simply depend on (seq "2.12") and on (emacs "25"). The problem with this solution is that we'd get tons of byte-compilation warnings, becaus even if seq-25.el is never used with Emacs 24.x, it will get byte-compiled. We were wondering if there would be a way to prevent byte-compilation only on some emacs versions, or if someone have a better solution to the problem. Cheers, Nico =2D-=20 Nicolas Petton http://nicolas-petton.fr --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQEcBAEBCAAGBQJWwyTzAAoJECM1h6R8IHkQ+pEH/iBPh4OgSPLHYd/+hoNyXjBd dwsDEK/yUwfncktvVNfALXn/2PCw25x6NmhpWjDw5f6/To69N8hUZ+edEOJa3nid PUDtRWUkTgb9eQWqa2kUQJmn7p2se/p6XmcnSSSRQQNVwL9cTUthGJPB+Tk6Lbpw knCsOyk6j0lTB8gwgD71vM+NvHe0oChaKen02Vni6WOCvM1h1l0lGr/dK/Xq6cCi c2VlkX1Sf5e6zT5kNzItHal7po1FBaxgeidCAVYhOwXv7N/EUMG87kvaMvleXrPX s/DEMoovoAp1B8/4YuvkPb1GmDqLmIjukmKSjAvG0PGI+kaOm0epk782Dsc7gOA= =4aYr -----END PGP SIGNATURE----- --=-=-=--