From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: How to distribute dynamic modules by themselves? Date: Wed, 23 Mar 2022 18:16:43 -0400 Message-ID: References: <951567BE-B2FA-4224-A369-B96469D2E083@gmail.com> <87y210apam.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31497"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Yuan Fu , Emacs developers To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 23 23:18:52 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nX9Jc-000817-I2 for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Mar 2022 23:18:52 +0100 Original-Received: from localhost ([::1]:51788 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nX9Jb-0002JI-8U for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Mar 2022 18:18:51 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:35154) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nX9Hg-0000wN-V6 for emacs-devel@gnu.org; Wed, 23 Mar 2022 18:16:56 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:35049) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nX9He-00036f-C4 for emacs-devel@gnu.org; Wed, 23 Mar 2022 18:16:52 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 7C4548061E; Wed, 23 Mar 2022 18:16:48 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id C6FA38051E; Wed, 23 Mar 2022 18:16:46 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1648073806; bh=RhSkNzEseL8KHPRxt+mrXlW1PyplB8exOyZ8NALMkjs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=aI9dpjSYzfVJ0tEXwWp7mFGF0rLGuV9HOZ/NSyaehZY5iy95c0YgiE/eKCeecNtdN arqJFMLnUe8hdO258i8zkUI6QM8rh5wLhpE3oX1498UT0salZjF0laeGk8f+imyIuC u1vyxyR6xjrSj7wlU3nIST+SMzVnu5mN0U+ACcNcy/1wxsob27es5TXmV1tiwPrzde mMmVefepliyM7TNBB5tDLnP2evz4XixyMn2NQl4YiYc/kcmmmaGrkW7Alw4UURMZbG R8PBBw/D0DEpS1lc6EUnFMPSP6oVCVBkbLkzyQFC1DuB9Y7O6k45Kq1dHqbj08sZk4 0f04iKo8Dpp2A== Original-Received: from ceviche (a213-22-142-170.cpe.netcabo.pt [213.22.142.170]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B4DCF12039E; Wed, 23 Mar 2022 18:16:45 -0400 (EDT) In-Reply-To: <87y210apam.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 23 Mar 2022 12:20:17 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:287402 Archived-At: Lars Ingebrigtsen [2022-03-23 12:20:17] wrote: > Yuan Fu writes: >> Is there any way to put a dynamic module on ELPA so that other >> packages could use it conveniently? > I'm not quite sure what the state of dynamic modules on ELPA is. > Stefan? Currently, there's only one such module,m i.e. `pq`. It's not well integrated yet. The way it's supposed to work (after Someone=E2=84=A2 codes it up) is that during `package-install` a chunk of ELisp in the attempts to compile the module. Then the same chunk of ELisp should (re)compile the module as/when needed when the ELisp package is loaded. Ideally, this is done from a function, so it's not done when the package is barely loaded but when that function is actually called (which is a more convincing evidence that the module is needed). Regarding distributing pre-compiled modules, there's currently no infrastructure for that. We could consider it, but it can only be a partial solution (we can't easily make sure we cover all possible architecures, ...), so the focus for now is in getting the automated/lazy-compilation working. Stefan