From: Nicolas Goaziou via Guix-patches via <guix-patches@gnu.org>
To: 68891@debbugs.gnu.org
Cc: mail@cbaines.net, csantosb@inventati.org
Subject: [bug#68891] [PATCH] gnu: emacs-org-board: Update to 1138-2.500fe02.
Date: Thu, 22 Feb 2024 11:52:46 +0100 [thread overview]
Message-ID: <871q94py81.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87eddgv6i1.fsf@inventati.org> (Cayetano Santos via Guix-patches via's message of "Tue, 13 Feb 2024 14:18:02 +0100")
Hello,
Cayetano Santos via Guix-patches via <guix-patches@gnu.org> writes:
> When one installs emacs-org-board, wget2-2.1.0 gets installed along with
> it as for emacs-substitute-variables, as you say, and the variable
> org-board-wget-program is bound to this hardcoded value.
Correct.
> Once one decides to upgrade wget2 to something different (say, in a
> different profile), this logic breaks. User needs to manually bind
> org-board-wget-program to whatever wget2 is after upgrading. At this
> point, wget2 becomes a native-input requirement.
This is not correct. No action is required from the user.
`org-board-wget-program' still points to the wget program defined as an
input to emacs-org-board, and will still be used at run time.
Of course, the user still can point `org-board-wget-program' to their
new and shiny wget binary, but this is not required.
I also suggest to keep wget (or wget2) as an input and use
`emacs-substitute-variables'.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2024-02-22 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:45 [bug#68891] [PATCH] gnu: emacs-org-board: Update to 1138-2.500fe02 Cayetano Santos via Guix-patches via
2024-02-13 11:21 ` Christopher Baines
2024-02-13 13:18 ` Cayetano Santos via Guix-patches via
2024-02-22 10:52 ` Nicolas Goaziou via Guix-patches via [this message]
2024-11-12 14:12 ` [bug#68891] [PATCH v1] " Cayetano Santos via Guix-patches via
2024-11-19 10:36 ` [bug#68891] Control message for bug #68891 Cayetano Santos via Guix-patches via
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=871q94py81.fsf@nicolasgoaziou.fr \
--to=guix-patches@gnu.org \
--cc=68891@debbugs.gnu.org \
--cc=csantosb@inventati.org \
--cc=mail@cbaines.net \
--cc=mail@nicolasgoaziou.fr \
/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/guix.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.