GNU bug report logs -
#65014
Configure Default Values
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 65014 in the body.
You can then email your comments to 65014 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65014
; Package
emacs
.
(Wed, 02 Aug 2023 12:17:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jacob Faibussowitsch <jacob.fai <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 02 Aug 2023 12:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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)
Reply sent
to
Po Lu <luangruo <at> yahoo.com>
:
You have taken responsibility.
(Wed, 02 Aug 2023 13:32:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jacob Faibussowitsch <jacob.fai <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 02 Aug 2023 13:32:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 65014-done <at> debbugs.gnu.org (full text, mbox):
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.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 31 Aug 2023 11:24:06 GMT)
Full text and
rfc822 format available.
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.