From: Cayetano Santos <csantosb@inventati.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: emacs packaging: do we need to pull existing dependencies ?
Date: Sun, 05 Feb 2023 11:50:21 +0100 [thread overview]
Message-ID: <87h6w08jeg.fsf@inventati.org> (raw)
In-Reply-To: <e9a4151bd3be69433b86f0e86030d528a967979c.camel@gmail.com>
>> Say for example emacs-org-roam@2.2.2: it requires emacs-org 9.4,
>> which is not specified in the package definition, meaning we always
>> pull the latest available. Do we have to, provided that emacs
>> releases with org? Maybe there is already a clear rule about this
>> topic, but to me this is not clear. We have package definitions with
>> both criteria.
> I think it's important to think about this in terms of forward
> compatibility. Is org-roam guaranteed to always work with "the current
> version of Emacs, whatever that may happen to be"? In that case, you
> could currently drop emacs-org. If it requires bleeding edge symbols
> on the other hand, or may freely decide that it will need them, adding
> emacs-org to the inputs is a good idea.
I don’t see your point. This is exactly the responsibility of the
package, declare its dependencies today, regardless of what the
dependencies will be in the future. This is what the ’package-requires’
field is for, including the version number of the dependencies.
If the dependencies of a given package are already there in emacs (say
org-9.2), why do we need to pull org-latest ? If in the future this
changes, an author decides he needs bleeding edge org features, and
changes the version number of org in the ’package-requires’ field, the
new package definition will propagage-require org-latest. All in all, we
may not predict future package needs, pulling dependencies just in case.
In any case, and whatever the decission, I think we should clearly state
the way to proceed somewhere, as currently we have a mix of both.
C.
next prev parent reply other threads:[~2023-02-05 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 7:44 emacs packaging: do we need to pull existing dependencies ? Cayetano Santos
2023-02-04 17:58 ` Liliana Marie Prikler
2023-02-05 10:50 ` Cayetano Santos [this message]
2023-02-05 19:46 ` Liliana Marie Prikler
2023-02-06 16:53 ` Simon Tournier
-- strict thread matches above, loose matches on Subject: below --
2023-01-31 8:13 Emacs " Cayetano Santos
2023-01-29 18:27 Cayetano Santos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6w08jeg.fsf@inventati.org \
--to=csantosb@inventati.org \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).