Re: Package Requiring a Commit?

[Jai Flack]

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