unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: rms@gnu.org
Cc: nickrob@snap.net.nz, jan.h.d@swipnet.se, emacs-devel@gnu.org,
	miles@gnu.org
Subject: Re: new image library "requirements"
Date: Tue, 19 Jun 2007 13:14:31 +0200	[thread overview]
Message-ID: <86r6o8tcvc.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <E1I0b91-0004Nu-BI@fencepost.gnu.org> (Richard Stallman's message of "Tue\, 19 Jun 2007 06\:41\:07 -0400")

Richard Stallman <rms@gnu.org> writes:

>     > Yes, where does it all end?  Emacs will build without alsa headers but
>     > presumably that leads to some loss of functionality (playing midi files,
>     > maybe?).  Should configure throw an error when these aren't found?
>
> The answer to that question isn't a theoretical one.  It is a matter
> of how important a given feature is as a feature of Emacs.
>
> For instance, for sound: how important a problem is it that people
> build Emacs and don't get sound, just because they didn't have the
> right headers installed?  On the other side, how big an
> inconvenience is it to be pressured into installing the headers,
> when you didn't want sound anyway?

We want to avoid having "underfeatured" Emacs binaries around without
people noticing: particularly bad track records have missing X11
support and missing XPM support (needed for color icons).

Requiring explicit options for suppressing such libraries (even if it
is just --without-panic) will mean that the output of
system-configuration-options (which is reported by report-emacs-bug)
will reflect this compilation configuration.  This makes error
diagnosis easier and provides a first pointer to the user before
actually sending the bug report.

When the user is not identical with the person compiling Emacs, this
might be even more relevant, though in all fairness, I think most of
the problems reported in this context have been from users making
their own compilations.

-- 
David Kastrup

  reply	other threads:[~2007-06-19 11:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17  0:07 new image library "requirements" Miles Bader
2007-06-18  6:01 ` Jan Djärv
2007-06-18  6:09   ` Nick Roberts
2007-06-18  7:34     ` David Kastrup
2007-06-18  8:18       ` martin rudalics
2007-06-18 15:37         ` Sascha Wilde
2007-06-18 15:39           ` Lennart Borgman (gmail)
2007-06-18 19:26       ` Eli Zaretskii
2007-06-19  5:54         ` Jan Djärv
2007-06-19  6:06           ` Eli Zaretskii
2007-06-19  7:28             ` David Kastrup
2007-06-19  7:53               ` Jason Rumney
2007-06-19 22:27               ` Richard Stallman
2007-06-20  1:08                 ` Stefan Monnier
2007-06-19 22:26         ` Richard Stallman
2007-06-20  1:07           ` Stefan Monnier
2007-06-20 17:35             ` Richard Stallman
2007-06-20  3:18           ` Eli Zaretskii
2007-06-20  5:38             ` David Kastrup
2007-06-20  5:50             ` Jan Djärv
2007-06-20  7:30               ` David Kastrup
2007-06-20  7:37                 ` Glenn Morris
2007-06-20 22:17               ` Jason Rumney
2007-06-20 17:35             ` Richard Stallman
2007-06-20 19:39               ` Jan Djärv
2007-06-21 17:32                 ` Richard Stallman
2007-06-19 10:41       ` Richard Stallman
2007-06-19 11:14         ` David Kastrup [this message]
2007-06-19 11:16         ` Nick Roberts
2007-06-19 12:09           ` Jan Djärv
2007-06-19 21:12             ` Nick Roberts
2007-06-20  5:43               ` Jan Djärv
2007-06-20 13:28               ` Richard Stallman
2007-06-18  7:30   ` David Kastrup

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=86r6o8tcvc.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=miles@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=rms@gnu.org \
    /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).