all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: new image library "requirements"
Date: Mon, 18 Jun 2007 09:30:48 +0200	[thread overview]
Message-ID: <86zm2x1zyv.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <46761FA4.8090403@swipnet.se> ("Jan Djärv"'s message of "Mon\, 18 Jun 2007 08\:01\:08 +0200")

Jan Djärv <jan.h.d@swipnet.se> writes:

> Miles Bader skrev:
>> I just tried compiling a new emacs, and the configure failed with:
>>
>>    configure: error: The following required libraries was not found:
>>         libgif/libungif libtiff
>>    Maybe some development libraries/packages are missing?
>>    If you don't want to link with them give
>>         --with-gif=no --with-tiff=no
>>    as options to configure
>>
>> While there's a case to be made for "requiring" (without options) X
>> libraries or even jpeg /png, I think requiring these is kind of silly.
>>
>> Tiff is fairly rarely used except in specialized applications.

Disagree: it is the dominant format for CMYK work.

>> The case with .gif is more vague, but it seems largely a legacy
>> format, and is getting more and more rare these days -- you see it
>> on old web sites, and people still use it for "animated" images
>> (which emacs doesn't support), but it seems kind of unusual to see
>> it for the kind of content which people might keep around.

Disagree: gifs still outnumber png files about 3:1 at least on the
web.

>> At the least, I'd drop the "requirement" for tiff.
>
> I asked the same thing, but David Kastrup was the only one who
> commented (granted, the subject line was not about image libraries):
>
>> It is quite common in prepress, and since Emacs includes stuff like
>> image-dired, it would appear reasonable to not omit it without
>> notice.

The idea behind the requirements was to not get the user an Emacs
version that does not have full capabilities without notice.  Since
image browsing is a part of Emacs, I feel that this is appropriate.
One could turn it into a very strong worded and visible warning
instead, possibly.

But the previous behavior of being somewhere in a yes-and-no summary
list (among items for which "no" does not imply a loss of
functionality, like for a particular memory allocation scheme) is not
likely to get the user to realize what happens.

-- 
David Kastrup

      parent reply	other threads:[~2007-06-18  7:30 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
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 [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

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

  git send-email \
    --in-reply-to=86zm2x1zyv.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=miles@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 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.