From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@newcastle.ac.uk (Phillip Lord) Newsgroups: gmane.emacs.help Subject: Re: using use-package Date: Fri, 14 Aug 2015 10:16:18 +0100 Message-ID: <87a8tudycd.fsf@newcastle.ac.uk> References: <67cb463e-41f6-4f37-91ee-15d0fdb5ba9f@googlegroups.com> <20150812180621.32265.2E673ABE@ahiker.mooo.com> <87bnebnyyl.fsf@newcastle.ac.uk> <87d1yrmb1i.fsf@newcastle.ac.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1439543814 8176 80.91.229.3 (14 Aug 2015 09:16:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Aug 2015 09:16:54 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Stefan Monnier Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Aug 14 11:16:45 2015 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 1ZQB6P-0002WU-HF for geh-help-gnu-emacs@m.gmane.org; Fri, 14 Aug 2015 11:16:41 +0200 Original-Received: from localhost ([::1]:45320 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQB6O-0007EG-Ie for geh-help-gnu-emacs@m.gmane.org; Fri, 14 Aug 2015 05:16:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40211) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQB6D-0007D9-SR for help-gnu-emacs@gnu.org; Fri, 14 Aug 2015 05:16:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZQB69-0006LA-1h for help-gnu-emacs@gnu.org; Fri, 14 Aug 2015 05:16:29 -0400 Original-Received: from cheviot22.ncl.ac.uk ([128.240.234.22]:56047) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQB68-0006Jo-RT for help-gnu-emacs@gnu.org; Fri, 14 Aug 2015 05:16:24 -0400 Original-Received: from smtpauth-vm.ncl.ac.uk ([10.8.233.129] helo=smtpauth.ncl.ac.uk) by cheviot22.ncl.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1ZQB62-0002ZG-FT; Fri, 14 Aug 2015 10:16:18 +0100 Original-Received: from jangai.ncl.ac.uk ([10.66.67.223] helo=localhost) by smtpauth.ncl.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1ZQB62-0000SE-G5; Fri, 14 Aug 2015 10:16:18 +0100 In-Reply-To: (Stefan Monnier's message of "Thu, 13 Aug 2015 17:19:07 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 128.240.234.22 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:106576 Archived-At: Stefan Monnier writes: >>> The core part of "Packaging" in the elpa.git world basically means: >>> - Start the package's main file with ";;; --- " >>> - Sprinkle a few ";;;###autoload"s. >>> - Add a "Package-Requires:" (when needed). >>> This is very straightforward and can be done from the very beginning >>> of development. >> I use use-package to load the modules in my personal configuration, >> which I don't intend to ever release or install as ELPA packages. Still, >> this is a minor use. > > For those, Package-Requires is probably unneeded (tho if you have such > things in your use-package you could move them there), I generally do not do dependency stuff with use-package. In this case, I would put a "require" statement into the secondary file. I think I will not go the root of Package-Requires. As I said in the multi-line discussion, I find Package-Requires: headers flawed, as they are comments and yet still have to be a valid sexp. >> Yes. I use cask (normally via the python wrapper), but elpakit is also >> an option here. > > Not sure about Cask, but IIUC elpakit will generate a package-archive, > whereas we just want to turn the source tree into a valid "installed ELPA > package" without going through "make a tarball, create an > archive-contents, package-install". > > I.e. all we want (to make those packages look like they were installed > via package.el) is to create/update a *-pkg.el and a *-autoloads.el > (we can add byte-compilation, but it's not indispensable). Indeed. Cask doesn't have that option at the moment. It's not hard, though (let ((dir (make-temp-name "cask"))) (cask-cli/package dir) (package-install-file (concat dir default-directory ".tar"))) that sort of thing (untested for demonstration purposes only). The easiest way to have a package look like it was installed via package.el is surely to install it via package.el! Phil