unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Omar Polo <op@omarpolo.com>,  emacs-devel@gnu.org
Subject: Re: [ELPA] new package: sndio.el
Date: Sun, 14 Nov 2021 13:35:09 -0500	[thread overview]
Message-ID: <jwvwnlasi2z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8735nyeggm.fsf@posteo.net> (Philip Kaludercic's message of "Sun,  14 Nov 2021 18:32:09 +0000")

Philip Kaludercic [2021-11-14 18:32:09] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> From what I see, if I were to download and run the package on a GNU
>>> System without sndio, there wouldn't be any clear error message
>>> indicating what went wrong, just an error message indicating that
>>> sndioctl has failed, right? (this is just from reading and using faulty
>>> mental evaluation). If the package is to be added to GNU ELPA, you
>>> should probably add a explicit error message (perhaps even at compile
>>> time) to clarify what is missing, and that the package isn't mean to
>>> work on this system.
>>
>> From where I stand, OTOH, I'd ask not to emit an error or warning during
>> compilation (e.g. I compile all the files in elpa.git and I don't have
>> sndio).  Similarly, don't sign an error when loading `sndio.el` (a
>> warning is tolerable).
>
> I did not consider that.  In that case a warning/error is certainly not
> acceptable.
>
> It should probably suffice to just throw an error when calling the
> autoloaded `sndio' command.

Signaling errors when the package is actually used makes a lot of
sense, yes.

Just to be clear: I haven't looked at the code, so I'm only speaking
on matters of principles here.


        Stefan




      reply	other threads:[~2021-11-14 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14  8:44 [ELPA] new package: sndio.el Omar Polo
2021-11-14 18:17 ` Philip Kaludercic
2021-11-14 18:27   ` Omar Polo
2021-11-14 18:46     ` Philip Kaludercic
2021-11-14 18:59       ` Omar Polo
2021-11-14 18:29   ` Stefan Monnier
2021-11-14 18:32     ` Philip Kaludercic
2021-11-14 18:35       ` Stefan Monnier [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=jwvwnlasi2z.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=op@omarpolo.com \
    --cc=philipk@posteo.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).