Upgrading packages: Difference between revisions
Jump to navigation
Jump to search
PaulEggleton (talk | contribs) (Tweak formatting, update and extend a bit) |
PaulEggleton (talk | contribs) (More formatting improvements; correct final step for current OE; add link to YP ref manual for buildhistory) |
||
| Line 8: | Line 8: | ||
= If you do not need to keep the last version of the package = | = If you do not need to keep the last version of the package = | ||
# Use | # Use <code>git mv recipes-xyz/recipename/recipename_1.0.bb recipes-xyz/recipename/recipename_2.0.bb</code> | ||
# Make | # Make further changes to <code>recipes-xyz/recipename/recipename_2.0.bb</code> as appropriate. | ||
# At the very minimum do a | # At the very minimum do a compilation test (<code>bitbake recipename</code>) to make sure the new package does at least fetch and compile. | ||
# Consider using buildhistory to check for changes between the versions. | # Consider using buildhistory to check for changes between the versions. See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference Manual. | ||
# Inspect the output of " | # Inspect the output of "git diff recipes-xyz/recipename/". Is this really what you want to commit? | ||
# Final step | # Final step - publish your work. See '''[[How to submit a patch to OpenEmbedded]]''' | ||
= If you do want to keep the last version of the package = | = If you do want to keep the last version of the package = | ||
Revision as of 13:12, 5 June 2014
Different layers have different policies for keeping versions of software around. OE-Core for example is fairly agressive about having one, good, recent version of the software than many older versions. Other layers may have different policies.
There are two cases we need to consider:
- You do want to keep the version of the bb file that is in OE now (somebody else needs this particular version)
- You don't.
If you do not need to keep the last version of the package
- Use
git mv recipes-xyz/recipename/recipename_1.0.bb recipes-xyz/recipename/recipename_2.0.bb - Make further changes to
recipes-xyz/recipename/recipename_2.0.bbas appropriate. - At the very minimum do a compilation test (
bitbake recipename) to make sure the new package does at least fetch and compile. - Consider using buildhistory to check for changes between the versions. See Maintaining Build Output Quality in the Yocto Project Reference Manual.
- Inspect the output of "git diff recipes-xyz/recipename/". Is this really what you want to commit?
- Final step - publish your work. See How to submit a patch to OpenEmbedded
If you do want to keep the last version of the package
Same as above, except instead of the first step:
cp recipes-xyz/recipename/recipename_1.0.bb recipes-xyz/recipename/recipename_2.0.bb git add recipes-xyz/recipename/recipename_2.0.bb