all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
To: Yuri Khan <yurivkhan@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [ANNOUNCE] Emacs 26.1 released
Date: Thu, 31 May 2018 11:09:31 -0500 (CDT)	[thread overview]
Message-ID: <alpine.GSO.2.20.1805311052290.27004@scrappy.simplesystems.org> (raw)
In-Reply-To: <CAP_d_8Xs0Yjz1nc3K_BceXavJmQMUfSczMmKHta5vAAOqACqOA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]

On Thu, 31 May 2018, Yuri Khan wrote:

> On Thu, May 31, 2018 at 10:35 PM Bob Friesenhahn
> <bfriesen@simple.dallas.tx.us> wrote:
>
>> Developers should be cognizant of the packages they are requiring to
>> be used.
>
> It’s not so easy. A library can be packaged under one name in Debian
> and a slightly different name in Red Hat, or distributed as one vs.
> multiple packages, or carried by one distribution but not the other.
> So, the error message that lists a missing library or header is pretty
> much the best you can get without delving into those differences.

The task of maintaining a configure script is definitely not easy. 
The benefits of making the configure script as user-friendly as 
possible is that then more users are using the latest version rather 
than a stale version provided by their operating system distribution.

In this case the configure.ac developer explicitly entered a 
pkg-config package name (including its major version) and so it was a 
developer decision to produce a specific pkg-config package name but 
used an indistinct generic meaningless name ("WEBKIT") in configure 
output that the user sees, as well as the terminal error message.

The project is able to maintain 1.1 million lines of lisp code and 
293k lines of ANSI C code which are presumably mostly correct, so it 
should be possible to suitably maintain the 5k lines of configure.ac 
code as so that ordinary end users are able to compile emacs as well.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

  reply	other threads:[~2018-05-31 16:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 14:14 [ANNOUNCE] Emacs 26.1 released Nicolas Petton
2018-05-28 14:38 ` Tino Calancha
2018-05-30 12:47 ` Byung-Hee HWANG (황병희, 黃炳熙)
2018-05-30 21:02 ` Phillip Lord
2018-05-30 23:20   ` Tak Kunihiro
     [not found]     ` <d128f41704af0d075e5a8c04b7d8f9e8.squirrel@cloud103.planethippo.com>
2018-06-01  7:29       ` Tak Kunihiro
2018-05-30 21:51 ` Bob Friesenhahn
2018-05-31  8:40   ` Robert Pluim
2018-05-31  9:11     ` joakim
2018-05-31 13:07     ` Bob Friesenhahn
2018-05-31 15:16       ` Eli Zaretskii
2018-05-31 15:34         ` Bob Friesenhahn
2018-05-31 15:45           ` Yuri Khan
2018-05-31 16:09             ` Bob Friesenhahn [this message]
2018-05-31 15:54           ` Lars Ingebrigtsen
2018-06-01  6:55             ` glitchy gotcha message (Was: [ANNOUNCE] Emacs 26.1 released) Van L
2018-05-31 16:04           ` [ANNOUNCE] Emacs 26.1 released Eli Zaretskii
2018-06-01  2:58           ` Python stack with vc and hg on 26.1 (was [ANNOUNCE] Emacs 26.1 released) Mike Kupfer
2018-06-06 14:48       ` [ANNOUNCE] Emacs 26.1 released Joshua Branson
2018-06-01  8:48   ` Eli Zaretskii

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=alpine.GSO.2.20.1805311052290.27004@scrappy.simplesystems.org \
    --to=bfriesen@simple.dallas.tx.us \
    --cc=emacs-devel@gnu.org \
    --cc=yurivkhan@gmail.com \
    /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.