Difference between revisions of "Upgrading packages"

From Openembedded.org
Jump to: navigation, search
(Removing recipes)
(8 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Do you know about the powers of [http://www.kernel.org/pub/software/scm/git/docs/git-mv.html <u>git-mv</u>]?  If you are upgrading a package you really should.
+
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.
  
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.
+
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.
  
 
= You do not need to keep the last version of the package =
 
= You do not need to keep the last version of the package =
  
# Use "[http://www.kernel.org/pub/software/scm/git/docs/git-mv.html <u>git-mv</u>] packages/$pkg/$file_v1.bb packages/$pkg/$file_v2.bb" so that we don't accumulate unecessary cruft.  Using the built-in rename function also ensures we can trace the changes for a package with "git log" even across upgrades.
+
# Use "[http://www.kernel.org/pub/software/scm/git/docs/git-mv.html <u>git-mv</u>] packages/$pkg/$file_v1.bb packages/$pkg/$file_v2.bb"
 
# make <u>further changes</u> to packages/$pkg/$file_v2.bb as appropriate.
 
# make <u>further changes</u> to packages/$pkg/$file_v2.bb as appropriate.
 
# At the very minimum do a <u>compilation test</u> "bitbake $file" to make sure the new package does at least fetch and compile.
 
# At the very minimum do a <u>compilation test</u> "bitbake $file" to make sure the new package does at least fetch and compile.
 
# inspect the output of "<u>git diff</u> packages/$pkg/".  Is this really what you want to commit?
 
# inspect the output of "<u>git diff</u> packages/$pkg/".  Is this really what you want to commit?
# Final step, <u>publish your work</u>.  "git commit packages/$pkg/ && git push"
+
# Final step, <u>publish your work</u>.  "git commit packages/$pkg/ && git push".
  
 
= You do want to keep the last version of the package =
 
= You do want to keep the last version of the package =
  
Same as above, except that between the first and second step you do
+
Same as above, except instead of the first step:
 
+
cp packages/$pkg/$file_v2.bb packages/$pkg/$file_v1.bb
+
git-add packages/$pkg/$file_v1.bb
+
 
+
Now, you may ask "Why rename the file first and then copy it back?"  Good question!  With using "git mv" to rename and then copying back we keep the "git log"-history forever.  Just "cp $a $b;git add $b" means we have a truncated history once $a gets removed.
+
 
+
= Removing recipes =
+
 
+
Although preventing the accumulation of cruft in the repository is good, you should take into account that distributions may be using a certain recipe and depend upon it. Therefore, before removing a recipe from the repository, do a grep in the 'conf/distro' directory. If the version you are going to remove is being explicitly used, send the respective patch to the development mailing list for 'RFC' first.
+
  
: This is too restrictive and I think above paragraph was added to this page without a directive from the core team who should have been the one to decide. preferred-om-2008-versions.inc looks down virtually all recipesIn essence, the above requirement for RFC translates into "all old versions have to accumulate in HEAD or an RFC for their removal sent".  I don't think that is what we want.  I will certainly not follow that like a slave for packages that I maintain (For example, I will update libassa in a minute to 3.5.0 without keeping 3.4.2 around and wasting my time on re-libtoolizing an obsolete version of a fringe package.  Sorry). --[[User:Laibsch|Laibsch]] 22:07, 18 May 2009 (UTC)
+
  cp packages/$pkg/$file_v1.bb packages/$pkg/$file_v2.bb
 +
  git-add packages/$pkg/$file_v2.bb
  
 
[[Category:Policy]]
 
[[Category:Policy]]

Revision as of 11:12, 7 November 2012

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:

  1. You do want to keep the version of the bb file that is in OE now (somebody else needs this particular version)
  2. You don't.

You do not need to keep the last version of the package

  1. Use "git-mv packages/$pkg/$file_v1.bb packages/$pkg/$file_v2.bb"
  2. make further changes to packages/$pkg/$file_v2.bb as appropriate.
  3. At the very minimum do a compilation test "bitbake $file" to make sure the new package does at least fetch and compile.
  4. inspect the output of "git diff packages/$pkg/". Is this really what you want to commit?
  5. Final step, publish your work. "git commit packages/$pkg/ && git push".

You do want to keep the last version of the package

Same as above, except instead of the first step:

cp packages/$pkg/$file_v1.bb packages/$pkg/$file_v2.bb
git-add packages/$pkg/$file_v2.bb
Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox