Do you know about the powers of mtn mv? If you are upgrading a package you really should.
Please follow these steps when upgrading a package to a more recent version. This is not to be seen as dogma, but rather as best practice. There are basically two cases we need to consider; a) you do want to keep the version of the bb file that is in OE now (somebody else needs this particular version) or b) you don't.
You do not need to keep the last version of the package
- Use "mtn mv packages/$pkg/$file_v1.bb packages/$pkg/$file_v2.bb" so that we don't accumulate unecessary cruft. Using the monotone built-in rename function also ensures we can trace the changes for a package with "mtn log" even across upgrades.
- make further changes to packages/$pkg/$file_v2.bb as appropriate
- At the very minimum do a compilation test "bitbake $file" to make sure the new package does at least fetch and compile
- inspect the output of "mtn diff packages/$pkg/|less". Is this really what you want to commit?
- Final step, publish your work. "mtn commit packages/$pkg/ && mtn pull && mtn merge && mtn push"
You do want to keep the last version of the package
Same as above, except that between the first and second step you do
cp packages/$pkg/$file_v2.bb packages/$pkg/$file_v1.bb mtn add packages/$pkg/$file_v1.bb
Now, you may ask "Why rename the file first and then copy it back?" Good question! With using "mtn mv" to rename and then copying back we keep the "mtn log"-history forever. Just "cp $a $b;mtn add $b" means we have a truncated history once $a gets removed.