From: Ricardo Wurmus <rekado@elephly.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 41188@debbugs.gnu.org, Jelle Licht <jlicht@fsfe.org>
Subject: [bug#41188] [PATCH] Do not propagate "emacs-org" in Emacs packages
Date: Sun, 17 May 2020 17:45:28 +0200 [thread overview]
Message-ID: <87ftbyh8fb.fsf@elephly.net> (raw)
In-Reply-To: <87h7wmwgor.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> On a more serious note, I have had _many_ issues with byte-compilation
>> of org-related anything over the years.
>
> I have not encountered such problems. I don't use much Org-related
> anything, either. Would you have any example in mind?
>
>> Wouldn't this mean that the list of packages that is touched by this
>> patch will be byte-compiled using the outdated org-mode that comes
>> with Emacs?
>
> It means exactly that.
>
>> Put another way, will all of these packages still work if I _do_ have
>> emacs-org installed in my profile?
>
> Good question. This is why I'm sending this patch for review in the
> first place.
I think it’s a good idea to ignore the version of org-mode that comes
with Emacs and assume that the latest version is installed, because they
are unfortunately far apart that I’m sure will cause problems.
I’m assuming that Org users generally will have a more recent org-mode
installed.
> OTOH, we currently force users to always update Org, possibly
> introducing, each time, breakage in their workflow, to get features that
> would work perfectly with bundled Org.
This is a general problem with Guix, though. Org-mode is no exception.
--
Ricardo
next prev parent reply other threads:[~2020-05-17 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 15:29 [bug#41188] [PATCH] Do not propagate "emacs-org" in Emacs packages Nicolas Goaziou
2020-05-11 16:02 ` Jelle Licht
2020-05-11 16:59 ` Nicolas Goaziou
2020-05-17 15:45 ` Ricardo Wurmus [this message]
2020-05-17 23:12 ` bug#41188: " Nicolas Goaziou
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=87ftbyh8fb.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=41188@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--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.