a) refer to a specific revision instead of master, moving target
versions as default are not good,
b) exlain to me how this is supposed to work at all?
I realize I am not familiar how sorcery works out this kind of spell.
SOURCE_URL is a git repo, the VERSION points to a branch? Is it downloading
)? If so, why not using simply that URL? This eases mirroring things.
But still, one needs to provide a source file name.
I tested with sorcery-{stable,test,devel} and summon did nothing for
libaccounts-glib. So I suspect the spell is incomplete or you have some
local sorcery hacks in place to magically work with this.
Really, I wonder: is this a complete spell at all?
Alrighty then,
Thomas
PS: The tarball resulting from such an URL still just contains a
directory named libaccounts-glib.git/. That is unfortunate. People
shouldn't be too lazy to do dammed releases!?!! Even using VERSION_1.18
is not safe. This is a branch which can change any day. We need to
refer to a specific commit at least. Then we can add a checksum to
DETAILS. I very much like checksums in DETAILS.
Attachment:
pgp5gJk1xHSDg.pgp Description: Digitale Signatur von OpenPGP