From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Adding Emms to ELPA (take 2), and a technical question Date: Fri, 24 Apr 2020 23:25:08 -0400 Message-ID: References: <87pnbwg0up.fsf@rabkins.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="75811"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Yoni Rabkin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 25 05:25:47 2020 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 1jSBRr-000JcH-Ol for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Apr 2020 05:25:47 +0200 Original-Received: from localhost ([::1]:57222 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jSBRq-0003Bh-Pw for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Apr 2020 23:25:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36996) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jSBRJ-0002Xt-FW for emacs-devel@gnu.org; Fri, 24 Apr 2020 23:25:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jSBRI-0004UW-G9 for emacs-devel@gnu.org; Fri, 24 Apr 2020 23:25:12 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:64251) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jSBRI-0004TZ-37 for emacs-devel@gnu.org; Fri, 24 Apr 2020 23:25:12 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C2393450573; Fri, 24 Apr 2020 23:25:10 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 222BC450570; Fri, 24 Apr 2020 23:25:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1587785109; bh=Ap00XcJw0s3BFmeyVw2/29/Z72nnizLCO8oi4Rhk+xI=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=C9velODMHPfbpbTWOURA0o9MvHuvEe7EuPe1k059tHkMduuUEJ40zfO4d3/famogj cldjUpXU1gzQ0vNK6LG4BlFWNv0HyNpncOTuh0MU4yKOjqYn/kzurhEs/IbDnIn28f 10brA76X9WF4ijVv3RB6snk7IphHuwRIEGmiuN3SJkV3GqTkxumEPVYWvqehvnVU4B jHaMS+RBhJmZ9lmz/Bu+At4hqjYDq2Ypc0LmD5HAa6uGfqNfNy/WWMaea/AeXoVqZf SDcqowADevx+/INKDmdmTh7BciM58c3v6O5nXjVwSXrULbnzZwZzujpG1iZhe65F/t sCcIoXAXe7vYw== Original-Received: from alfajor (unknown [104.247.241.114]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id CA210120769; Fri, 24 Apr 2020 23:25:08 -0400 (EDT) In-Reply-To: <87pnbwg0up.fsf@rabkins.net> (Yoni Rabkin's message of "Fri, 24 Apr 2020 15:06:22 -0400") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/04/24 22:48:09 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:247735 Archived-At: > The main issue back then was that Emms was a copyright mess. Stefan > Monnier helped me figuring out who to contact and I've fixed that since > (took a while). To the best of my knowledge, everyone who has code in > Emms has an assignment on file. Emms has an AUTHORS file which is kept > up-to-date. Everyone there should also appear in the FSF records. Great news, thank you! > Stefan also said that ELPA packages need to have their .el files at the > top-level. However, Emms has its files in a lisp/ directory. This is > still the case, and I would like to keep it that way because Emms has a > lot of files and a lisp/ directory keeps things tidy. Is this still a > requirement for ELPA? Yes, and you even wrote it right: it's a property of ELPA (and not specific to GNU ELPA), so it affects MELPA just as well. This comes from the fact that only top-level files are scanned for `;;;###autoload` cookies when the package is installed. You can work around this problem with extra work, tho: build your own autoloads file for the files in `lisp/*.el` and distribute it as if it were a "source" file. The Hyperbole package does that for its `kotl` subdirectory: they "manually" builds&updates a `kotl/kotl-autoloads.el` file (the rule to update it is in a Makefile), and then in `hyperbole.el` they have: ;;;###autoload (load "kotl/kotl-autoloads" nil 'nowarn) > Emms also comes with a small piece of code that needs to be compiled in > order to use taglib (https://taglib.org/). The code is in a src/ > directory in the Emms distribution. I understand that there is no way to > get ELPA to compile something as a part of the installation. Yes, there is. You can put something like: (eval-when-compile (call-process "make")) in your main file, for example. > We can forgo any compilation at the ELPA installation stage as long as > people get to read the excellent Emms manual which explains how (and > why) to compile that bit of code. Would any of this be a problem for > adding Emms to ELPA? These will require extra work on your part, but other than that, no, they don't impact your ability to add the package to GNU ELPA. > We (the Emms developers) are desperately looking for a better way to > give Emms access to taglib other than compiling glue code like we do > now. We really don't want to ship C, or C++, or Perl, or anything except > elisp with Emms. One option we are currently exploring is to ask the > user to install an existing package such as pytaglib (a GPLv3 python > wrapper around taglib). Is there any more elegant way to get access to > taglib through Emacs that anyone can suggest? I'm afraid I don't have a better solution to offer. Stefan