[OE-core] About auto-upgrade-helper's enhancement
Alexander Kanavin
alexander.kanavin at linux.intel.com
Thu Nov 30 07:26:23 UTC 2017
On 11/30/2017 05:27 AM, Paul Eggleton wrote:
> So for manual (or should I say semi-automatic) recipe upgrades, our primary
> tool is "devtool upgrade" - at the moment it is true that there are things
> that the AUH can do that devtool upgrade can't (e.g. auto-detecting the latest
> upstream version, handling LIC_FILES_CHKSUM, etc.), but I believe Alex will be
Both of these are already fixed, patches sent :)
> working on some of those and then will be moving the AUH to use devtool
> upgrade itself so that we don't have two codebases for the same task. We don't
> plan to deprecate manual usage of the AUH, but if there are use cases that
> devtool upgrade cannot currently handle, then assuming they fit I would like
> to handle them there first and point most users at devtool upgrade rather than
> manually running the AUH, since devtool upgrade is much more suited to
> enabling the work that follows on when an upgrade cannot be completed
> automatically.
Porting AUH to use devtool is in progress now, I got a first successful
upgrade yesterday. I'd say that for someone who regularly needs to
upgrade recipes, AUH (on top of devtool) is a useful thing to run
locally, as it can mass-create commits, and do some preliminary,
automatic build and even runtime testing - things that devtool doesn't
do and shouldn't. Then those commits can be further fixed manually.
Alex
More information about the Openembedded-core
mailing list