11

I have a package for interacting with GRASS GIS processes, available on MELPA. The rate of development and number of users are both quite low, so there's no need for a mailing list or any formal communications with my users.

However, I've just introduced some changes to the configuration options that will require some attention from my users - how can I communicate this to them, given that for most of them all they will see is the updated package coming in from MELPA? Is there a way to pass a message on to users that they will see the first time they run code after a certain change has been made? What is best-practice in this regard?

Tyler
  • 21,719
  • 1
  • 52
  • 92
  • 1
    I think this should be closed as "opinion-based". –  Oct 30 '15 at 16:39
  • 7
    You can use the method `magit` [uses](https://github.com/magit/magit/blob/2f1a0379a4503d235b8bdbb1664938aa24960068/lisp/magit.el#L2583) to warn users about incompatible `git` version.. basically conditionally displaying messages using `display-warning`. – Kaushal Modi Oct 30 '15 at 16:45
  • 11
    @lunaryorn "is there a way to pass a message to users via the package system?" isn't opinion based. Best-practices may or may not be, depending on whether package.el or the different repositories have an established method in place for passing info on to users. – Tyler Oct 30 '15 at 17:35

1 Answers1

4

I think the answer is that you're looking at the wrong place: try to solve the more general problem where the user installs your package maybe by hand, or via some other package system, or via ELPA but in a 100% automated way (so he won't see any message that may show up at that point).

IOW do it with code within your package, which tries to recognize the problematic situation and emit a warning/error accordingly at that time (i.e. at the time the package is used, rather than when it's installed or compiled).

Stefan
  • 26,154
  • 3
  • 46
  • 84