Re: 02/02: gnu: libical: Add upstream patch to preserve API compatibility.

[Marius Bakke]

Ludovic Courtès <address@hidden> writes:

> Howdy!
>
> address@hidden skribis:
>
>> +               (list (origin
>> +                       (method url-fetch)
>> +                       (uri (string-append
>> +                             "https://github.com/libical/libical/commit/";
>> +                             
>> "ae394010c889e4c185160da5e81527849f9de350.patch"))
>
> 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):
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=7670efefe4fb4aca12cb19ea5d89ff37c48e3ea6

signature.asc
Description: PGP signature