From: Jai Flack <jflack@posteo.net>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Package Requiring a Commit?
Date: Thu, 05 May 2022 14:40:16 +0000 [thread overview]
Message-ID: <878rrgyre7.fsf@posteo.net> (raw)
In-Reply-To: <87fsloe5a4.fsf@gnu.org> (Tassilo Horn's message of "Thu, 05 May 2022 10:37:47 +0200")
Tassilo Horn <tsdh@gnu.org> writes:
> Jai Flack <jflack@posteo.net> writes:
>
>>> This should work, just use next version:
>>>
>>> ;; Package-Requires: ((emacs "29"))
>>>
>>> Then people running Emacs which was built recently from master will be
>>> able to install your package, because they're "already on 29".
>>
>> Thanks that solves one of the issues. Is there no good solution to the
>> other? I can imagine some users building from master for a specific
>> feature (say, PGTK) and then not updating.
>
> For something like "at least as new as commit XXX" Emacs would need to
> carry its complete commit graph with it in order to check that
> requirement.
>
> So it's best to just require emacs 29. I personally have no big empathy
> for people running outdated development snapshots [1] but if you do, it
> shouldn't be too hard to fail gracefully by testing for
> functions/variables you need using (f)boundp.
>
> Bye,
> Tassilo
>
> [1] Simply because during development it may happen that new things are
> tweaked/renamed many times until finished.
I'm not necessarily after requiring specific commits but yes I suppose
something like that isn't a reasonable expectation.
--
Thanks,
Jai
next prev parent reply other threads:[~2022-05-05 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:44 Package Requiring a Commit? Jai Flack
2022-05-04 12:59 ` Filipp Gunbin
2022-05-05 7:46 ` Jai Flack
2022-05-05 8:37 ` Tassilo Horn
2022-05-05 14:40 ` Jai Flack [this message]
2022-05-05 13:43 ` Filipp Gunbin
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=878rrgyre7.fsf@posteo.net \
--to=jflack@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=tsdh@gnu.org \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.