unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: development practices for ELPA packages
Date: Thu, 19 Nov 2020 08:40:55 +0100	[thread overview]
Message-ID: <87mtzdztdk.fsf@gmx.de> (raw)
In-Reply-To: <87blfuz69q.fsf@rabkins.net> (Yoni Rabkin's message of "Wed, 18 Nov 2020 16:47:45 -0500")

Yoni Rabkin <yoni@rabkins.net> writes:

> Hello,

Hi,

> I currently have Emms and rt-liberation in ELPA. Users of those packages
> are happy with this. However, as a developer I'm less happy. I would
> like to ask for help in learning how people with packages in ELPA
> develop them.
>
> Right now I'm working on the next release of rt-liberation. I would like
> to tell Emacs: "load all of the ELPA packages normally, but when you get
> to rt-liberation please load my local, non-packaged, version from
> /devel/rt-liberation"
>
> I know I can give the package manager a list of packages to load, but
> that doesn't help me. I want to tell the package manage which package
> _not_ to load, and what to load instead.
>
> How do people who work on ELPA packages manage this?

I would call "make archive" on the top level of the ELPA directory. And
then I would declare a local ELPA archive with higher priority, like

(add-to-list 'package-archives
             '("local" . "/home/albinus/src/elpa/archive/packages/"))

(add-to-list 'package-archive-priorities
	     '("local" . 3))
(add-to-list 'package-archive-priorities
	     '("gnu" . 2))
(add-to-list 'package-archive-priorities
	     '("melpa" . 1))

> Thank you in advance.

Best regards, Michael.



      parent reply	other threads:[~2020-11-19  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 21:47 development practices for ELPA packages Yoni Rabkin
2020-11-18 22:10 ` Stefan Monnier
2020-11-18 23:36 ` Stephen Leake
2020-11-20 15:04   ` Yoni Rabkin
2020-11-20 15:22   ` Stefan Monnier
2020-11-19  7:40 ` Michael Albinus [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87mtzdztdk.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=yoni@rabkins.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).