all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yoni Rabkin <yoni@rabkins.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Adding Emms to ELPA (take 2), and a technical question
Date: Thu, 28 May 2020 22:46:53 -0400	[thread overview]
Message-ID: <87o8q7qwyq.fsf@rabkins.net> (raw)
In-Reply-To: <jwvblm86bf2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 27 May 2020 22:36:50 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> outside of using elpa. For instance, I know that there are people who
>> package Emms for Debian and other OS' using their own package
>> managers. I don't want to rock their boat if possible.
>
> Those people can package ELPA packages their eyes closed (try `apt
> search elpa-` to see why I think so). They will likely stop using their
> ad-hoc packaging once it's available via GNU ELPA and will use their
> generic support for packaging ELPA packages instead.
>
>> I made a file in the top-level of the emms distribution named
>> emms-elpa.el. emms-elpa.el contains the headers (Author, Version,
>> Package-Requires, etc.), followed by:
>
> The file that contains those headers *has* to be called <pkg>.el, so if
> you call it `emms-elpa.el` the package will have to be called `emms-elpa`.
>
>> ;;;###autoload (load "lisp/emms-auto" nil 'nowarn)
>
> LGTM.
>
>> You can see it here:
>> https://git.savannah.gnu.org/cgit/emms.git/tree/emms-elpa.el
>>
>> lisp/emms-auto.el is generated by lisp/Makefile to contain autoloads for
>> the .el files under lisp/
>
> Perfect.
>
>> I don't understand how that would be enough to provide a valid load-path
>> to the files in the lisp/ directory though.
>
> That won't be enough.  You probably want to add
>
>     (add-to-list 'load-path (directory-file-name (or (file-name-directory load-file-name) (car load-path))))
>
> to that `lisp/emms-auto.el` file.
>
>
>         Stefan

Does it makes sense for me to package Emms up in a ELPA-format archive,
load it into an local Emacs instance here, and see if it all works
before pinging the list again?

This would allow me to continue modifying things on my branch of Emms
here and check that it works for myself. All this without polluting the
main branch of Emms, or bugging y'all before everything is good to go.

-- 
   "Cut your own wood and it will warm you twice"



  parent reply	other threads:[~2020-05-29  2:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 19:06 Adding Emms to ELPA (take 2), and a technical question Yoni Rabkin
2020-04-25  3:25 ` Stefan Monnier
2020-04-28 13:28   ` Yoni Rabkin
2020-04-28 15:06     ` Robert Pluim
2020-04-28 16:02       ` Yoni Rabkin
2020-04-29  3:22       ` Richard Stallman
2020-04-29  8:13         ` Robert Pluim
2020-04-30  2:32           ` Richard Stallman
2020-04-29 11:53         ` Yoni Rabkin
2020-04-30 14:43         ` Yoni Rabkin
2020-05-01  2:52           ` Richard Stallman
2020-05-01  6:32             ` Joost Kremers
2020-05-01 14:07               ` Arthur Miller
2020-05-01 14:42                 ` Joost Kremers
2020-05-01 14:51                   ` Arthur Miller
2020-04-29 10:07       ` Basil L. Contovounesios
2020-04-29 12:45         ` Stefan Monnier
2020-05-27 19:44   ` Yoni Rabkin
2020-05-28  2:36     ` Stefan Monnier
2020-05-28  5:34       ` Sean Whitton
2020-05-29  2:46       ` Yoni Rabkin [this message]
2020-06-15 19:32 ` Yoni Rabkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8q7qwyq.fsf@rabkins.net \
    --to=yoni@rabkins.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.