From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Re: package.el changes before the feature freeze Date: Fri, 12 Oct 2012 11:58:03 +0800 Message-ID: <87wqywbaus.fsf@gnu.org> References: <87ipau51jh.fsf@gnu.org> <87626qk5xo.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1350014295 5770 80.91.229.3 (12 Oct 2012 03:58:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Oct 2012 03:58:15 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Daniel Hackney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 12 05:58:22 2012 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 1TMWOD-0003Lj-OQ for ged-emacs-devel@m.gmane.org; Fri, 12 Oct 2012 05:58:21 +0200 Original-Received: from localhost ([::1]:50899 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMWO7-0005Wj-DD for ged-emacs-devel@m.gmane.org; Thu, 11 Oct 2012 23:58:15 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:39886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMWO4-0005WU-Qp for emacs-devel@gnu.org; Thu, 11 Oct 2012 23:58:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TMWO3-0006Wi-Jb for emacs-devel@gnu.org; Thu, 11 Oct 2012 23:58:12 -0400 Original-Received: from mail-pb0-f41.google.com ([209.85.160.41]:64555) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TMWO3-0006We-DK for emacs-devel@gnu.org; Thu, 11 Oct 2012 23:58:11 -0400 Original-Received: by mail-pb0-f41.google.com with SMTP id rq2so2785980pbb.0 for ; Thu, 11 Oct 2012 20:58:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=wbaEA/GDM6qdY1MU/0UrE8WLj0HdzjSMiZfheqZWm3A=; b=rvClAb/ydS3rwn19iUSBaq7s1UqfSRo2iaiYWJzZMcHhJIhgvP9jLl/ZQsRY/UZsJV 50JPmUcwaE4SbSIp89K8mPSGKBuBxfYDlH3hfKyqB9x2Om7cXbEHAYWvia3Lo4MpKdGm vjIwp2YZeA6gnqsNd0vsUSMpVlp6JAG5NzvJEQdJL1C/mizra2rbN4uW895fekF7usOZ x/8Ihna0ufFjq3zrIyz3kO/UL8oX+Fw8WOMt70OxK8617hGhpxc3jErIjBhHRkRpl4Wt vM3YfxG1lnhL773/zpfFe68JtesUsNlc4Y8iyc8fxtG80hA5xZWtcXRoc2vVO7e7ddPl kNxQ== Original-Received: by 10.68.202.168 with SMTP id kj8mr10084050pbc.8.1350014289746; Thu, 11 Oct 2012 20:58:09 -0700 (PDT) Original-Received: from ulysses ([155.69.17.137]) by mx.google.com with ESMTPS id x6sm3638518pav.29.2012.10.11.20.58.06 (version=SSLv3 cipher=OTHER); Thu, 11 Oct 2012 20:58:08 -0700 (PDT) In-Reply-To: (Daniel Hackney's message of "Tue, 9 Oct 2012 17:39:00 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.160.41 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:154291 Archived-At: Daniel Hackney writes: > But the main point is: I think we would be well-served by pulling > these changes into 24.3 because it does not affect the user interface > at all and is therefore not going against the idea of a feature freeze My major concern is that third party packages which use existing functions in package.el, whose calling conventions are changed by this patch, would experience incompatibilities. This is not a show stopper for the post-24.3 development tree, since we will have lots of time to find out what compatibility problems exist and adapt accordingly. But I don't think it's suitable for 24.3; I don't want 24.3's freeze to drag on for too long. > I also remember having some trouble with installing or resuming an > aborted install and getting "file exists" errors. I'd have to dig a > little to remember what exactly was happening; if I find anything I'll > start a new thread about it. Any such bugs would be orthogonal to the defstruct cleanup, and should be reported and addressed separately.