[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 02/02: gnu: libical: Add upstream patch to preserve API compatibilit
Re: 02/02: gnu: libical: Add upstream patch to preserve API compatibility.
Wed, 05 Feb 2020 22:29:38 +0100
Notmuch/0.29.3 (https://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu)
Ludovic Courtès <address@hidden> writes:
> address@hidden skribis:
>> + (list (origin
>> + (method url-fetch)
>> + (uri (string-append
>> + "https://github.com/libical/libical/commit/"
> IIRC, those generated patches are not stable, like generated tarballs,
> no? What are the available options?
I haven't seen GitHub change such generated patch files yet[*], but I do
agree it's "fragile", because they can be difficult to reproduce when
GitHub inevitably disappears, or _do_ change the format.
I wonder if it's feasible to use Guile-Git to generate the patches
instead, at the expense of having to download the entire repository
for the purpose of extracting one or more (substitutable) patches.
[*] There was one instance where it had changed, but that was a merge
commit(!), which is a pretty extreme case (whoops):
Description: PGP signature