On Tuesday 25 November 2014 17:51:05 Paul Barker wrote: > On 25 November 2014 at 17:28, Paul Eggleton > <[email protected]> wrote: > > I've been looking at how to make it easier for application and system > > component developers to get their work done using the tools we provide, > > and I believe this patchset is a piece of the solution. There's still a > > number of other pieces to come, but this should be usable on its own. > > ... > > Comments/questions/suggestions welcome! > > This sounds great and looks like it will make some regular tasks quite > a bit easier! > > One thing which may be useful within recipetool or devtool is a single > command to create patch files (using `git format-patch`), put them > into the relevant directory and add the file names to SRC_URI. > Obviously this assumes the external source tree is a git repo and we > can trace the local modifications back to either an external master > branch or an initial state after extracting a source archive. I'm just > thinking out loud here though, depends if other people think that work > flow is common enough to be worth creating a shortcut for.
We've been thinking in this direction and it seems like a natural extension to me, and one that I do hope to add. The tricky part is as you say, reconciling the commits you have in the git tree with the patches you have in the recipe, particularly when the user might have modified one or more of those commits. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
