From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Installing binaries with package.el Date: Tue, 07 Feb 2017 10:07:27 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87d1euniog.fsf@flea> References: <3fdcbe78-969e-f9e1-2a9d-a5f8494c35b3@mit.edu> <8760kmtvpu.fsf@mbork.pl> <35ae3a71-f8da-3405-6966-38337d8e74e0@gmail.com> <871svatqh0.fsf@mbork.pl> <76433d89-f381-b805-4501-c9c8b8f7a275@gmail.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1486481227 30408 195.159.176.226 (7 Feb 2017 15:27:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 7 Feb 2017 15:27:07 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 07 16:27:04 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cb7fZ-0007bx-7V for ged-emacs-devel@m.gmane.org; Tue, 07 Feb 2017 16:27:01 +0100 Original-Received: from localhost ([::1]:54808 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cb7fe-0001PL-D8 for ged-emacs-devel@m.gmane.org; Tue, 07 Feb 2017 10:27:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58495) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cb7Mv-0002Jl-QQ for emacs-devel@gnu.org; Tue, 07 Feb 2017 10:07:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cb7Ms-0000Rd-My for emacs-devel@gnu.org; Tue, 07 Feb 2017 10:07:45 -0500 Original-Received: from [195.159.176.226] (port=53628 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cb7Ms-0000QZ-GY for emacs-devel@gnu.org; Tue, 07 Feb 2017 10:07:42 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cb7Mj-00074v-Sq for emacs-devel@gnu.org; Tue, 07 Feb 2017 16:07:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 26 Original-X-Complaints-To: usenet@blaine.gmane.org X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never Cancel-Lock: sha1:J1KR/wg6faUjmsfBszOmEbF9kXo= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:212096 Archived-At: On Tue, 7 Feb 2017 08:12:21 -0500 Clément Pit-Claudel wrote: CP> My case is a bit different. The binary is just a bash wrapper around an Emacs CP> Lisp program, so I don't have compilation-related issues; I do, however, want my CP> users to be able to call the program easily, which probably means that I want to CP> create binaries outside of my package's installation folder (which in turns has CP> consequences on uninstallation behaviour: deleting the installation folder isn't CP> enough). There's a similar concern about installing Emacs modules from ELPA--they have to be compiled and installed at some point. I think the best option may be to split binaries off to a new repo: 1) add support for binary package dependencies to ELPA packages. This would be something like a cond based on arch + OS, and would only look at GNU ELPA binary packages. 2) set up a GNU ELPA autobuilt binaries repository to support (1) for modules and binaries that are only meaningful in an Emacs context. The alternatives I see are to a) support binaries *inside* the GNU ELPA, which was not designed for it, or b) support binaries inside ELPA packages, which were not designed for that either. Maybe there are others? Ted