On 12-01-12 11:20 AM, Brian Hutchinson wrote:
On Thu, Jan 12, 2012 at 11:00 AM, Bruce Ashfield
<[email protected]> wrote:
The bitbake AUTOREV code should take care of updating the clone
of your local repo in downloads/git2. I take it that this isn't
happening ?
... haven't tried ... was just sticking to the example in the
documentation which says to push changes and do a cleanall. The spin
Good point. I hadn't noticed that it was in there. Worth trying
without it, and raising a bug if it isn't required. It's
bitbake internals rather than kernel at play here, so I'm far
from authoritative about what should or shouldn't work.
time on my dev machine wasn't too bad but long enough to get old quick
if I had to do it often.
Agreed!
It should be (largely) as simple as that. We could create something
simple and throw it in with the meta-kernel-dev layer if there's any
interest in adding it.
Just wanting to know what the "best practice" is as I have lots of
platforms to support.
I prefer to work this way, since managing patches in a source git
repository is much easier for me. If you only have a few patches,
then they can just be pushed on top and added to the SRC_URI, but
you'd be doing more development under tmp/work/ in that case .. and
I'm paranoid about losing things :)
Cheers,
Bruce
Regards,
Brian
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
