From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.help Subject: Re: Elpa packages and Makefiles Date: Wed, 01 Oct 2014 18:11:35 +0800 Message-ID: <87oatwrtew.fsf@ericabrahamsen.net> References: <877g3j8dg9.fsf@ericabrahamsen.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1412158339 22283 80.91.229.3 (1 Oct 2014 10:12:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Oct 2014 10:12:19 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 01 12:12:11 2014 Return-path: Envelope-to: geh-help-gnu-emacs@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 1XZGtH-0003zD-G7 for geh-help-gnu-emacs@m.gmane.org; Wed, 01 Oct 2014 12:12:11 +0200 Original-Received: from localhost ([::1]:54603 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZGtH-0006gg-22 for geh-help-gnu-emacs@m.gmane.org; Wed, 01 Oct 2014 06:12:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZGt0-0006gU-QE for help-gnu-emacs@gnu.org; Wed, 01 Oct 2014 06:12:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XZGsu-0006KR-I4 for help-gnu-emacs@gnu.org; Wed, 01 Oct 2014 06:11:54 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:34126) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XZGsu-0006KH-BY for help-gnu-emacs@gnu.org; Wed, 01 Oct 2014 06:11:48 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XZGst-0003ph-Bk for help-gnu-emacs@gnu.org; Wed, 01 Oct 2014 12:11:47 +0200 Original-Received: from 114.248.29.143 ([114.248.29.143]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Oct 2014 12:11:47 +0200 Original-Received: from eric by 114.248.29.143 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Oct 2014 12:11:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 114.248.29.143 User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:9Dn6VVLthaw0zBT2vgkuM2l+opE= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:100197 Archived-At: Stefan Monnier writes: >> will Elpa deployment honor an existing Makefile (in which case, which >> targets are used?), ignore it, or conflict -- ie I should .elpaignore it >> or something. > > package.el currently just ignores the Makefile. > It also ignores the .texi files, by the way (sadly). Okay I'm finally actually getting around to this, playing with a local deployment to see how it works, and still have a few questions (just one for now). I've got this package in Github as well, so I'm leaving it there, and moving local development to a subtree in elpa/packages. I started out with putting all the lisp files under a lisp/ directory in the main package directory (for reasons that now escape me). That includes the main PACKAGE.el entry-point file. I'd prefer not to mess with this, for the sake of existing users. Is there any sort of crutch I can use to both allow Elpa to create its top-level PACKAGE-pkg.el file (and put the lisp/ directory on the load path), and also not disturb users who are running from Github and have manually put lisp/ into their load path? Perhaps, if the "crutch" is simple, I could put it in a separate "elpa" branch that gets rebased on top of master, then push master to Github, and elpa to Elpa? Thanks, Eric