RFC: snapcraft sources keyword for parts

[Oliver Grawert]

hi,
Am Freitag, den 06.11.2015, 09:41 -0800 schrieb
robert_joslyn at selinc.com:

> Something else that I just came across, and that you may want to keep
> in 
> mind, is how to deal with patching. Frequently, we maintain small
> patch 
> sets for upstream repositories that we use. With Snapcraft, I don't
> really 
> have a clean way of fetching upstream sources, fetching internal
> patches, 
> and applying patches before the compile. 
> 
> One very generic way of dealing with this is to provide a pre-compile
> hook 
> that would allow Snapcraft to call out to a script after pulling but 
> before attempting the compile. This would provide a way to patch the 
> sources, or do any other needed manipulation of the source before the
> compile. Perhaps a nicer way is to have additional keywords for the
> source 
> type that would allow fetching of patches and automatically applying
> them.
> 
well, or you could simply maintain the patches in a github (or
launchpad) tree in a forked upstream branch that you use in your
snapcraft.yaml ...

ciao
	oli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 173 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/snappy-app-devel/attachments/20151106/f4d9e172/attachment.pgp>