GNU bug report logs - #65014
Configure Default Values

Previous Next

Package: emacs;

Reported by: Jacob Faibussowitsch <jacob.fai <at> gmail.com>

Date: Wed, 2 Aug 2023 12:17:01 UTC

Severity: normal

Done: Po Lu <luangruo <at> yahoo.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Po Lu <luangruo <at> yahoo.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#65014: closed (Configure Default Values)
Date: Wed, 02 Aug 2023 13:32:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Wed, 02 Aug 2023 21:31:02 +0800
with message-id <87wmydbmg9.fsf <at> yahoo.com>
and subject line Re: bug#65014: Configure Default Values
has caused the debbugs.gnu.org bug report #65014,
regarding Configure Default Values
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
65014: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65014
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Jacob Faibussowitsch <jacob.fai <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Configure Default Values
Date: Wed, 2 Aug 2023 08:16:19 -0400
Hello,

TL;DR: What packages does configure enable by default, i.e. do not require a --with-PACKAGE flag to explicitly enable? Moreover, what are the best practices for configuring emacs that don’t require min-maxing your configuration options every time.

——

I like to configure my emacs install to be as (reasonably) fully featured as possible, so I peruse the ./configure --help options from time to time to see if any new packages are available. If I notice a package I don’t have in my list of --with-package I add it, and reconfigure. 

But my configure command is now pretty long, and it strikes me that this brittle in the face of changes to configure. Suppose there is a change in best practices, and now --with-FOO is better than --with-BAR, but because I have --with-BAR (and forgot to remove it), configure won’t look for FOO. My emacs conf will be slightly suboptimal (perish the thought!) and I won’t be any the wiser.

Best regards,

Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)



[Message part 3 (message/rfc822, inline)]
From: Po Lu <luangruo <at> yahoo.com>
To: Jacob Faibussowitsch <jacob.fai <at> gmail.com>
Cc: 65014-done <at> debbugs.gnu.org
Subject: Re: bug#65014: Configure Default Values
Date: Wed, 02 Aug 2023 21:31:02 +0800
Jacob Faibussowitsch <jacob.fai <at> gmail.com> writes:

> Hello,
>
> TL;DR: What packages does configure enable by default, i.e. do not
> require a --with-PACKAGE flag to explicitly enable? Moreover, what are
> the best practices for configuring emacs that don’t require min-maxing
> your configuration options every time.
>
> ——
>
> I like to configure my emacs install to be as (reasonably) fully
> featured as possible, so I peruse the ./configure --help options from
> time to time to see if any new packages are available. If I notice a
> package I don’t have in my list of --with-package I add it, and
> reconfigure.
>
> But my configure command is now pretty long, and it strikes me that
> this brittle in the face of changes to configure. Suppose there is a
> change in best practices, and now --with-FOO is better than
> --with-BAR, but because I have --with-BAR (and forgot to remove it),
> configure won’t look for FOO. My emacs conf will be slightly
> suboptimal (perish the thought!) and I won’t be any the wiser.
>
> Best regards,
>
> Jacob Faibussowitsch
> (Jacob Fai - booss - oh - vitch)

Hi, questions about building Emacs should be directed to
help-gnu-emacs <at> gnu.org, not the bug tracker.  To answer them, however,
refer to INSTALL, which explains available configuration options in
detail.

Generally speaking, running `configure' without any arguments will
produce an Emacs with a configuration that is reasonable for most
users.


This bug report was last modified 1 year and 351 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.