Hello community,
here is the log from the commit of package llvm for openSUSE:Factory checked in
at 2016-10-18 10:37:06
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/llvm (Old)
and /work/SRC/openSUSE:Factory/.llvm.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "llvm"
Changes:
--------
--- /work/SRC/openSUSE:Factory/llvm/llvm.changes 2016-10-10
17:26:36.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.llvm.new/llvm.changes 2016-10-18
10:37:07.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Oct 7 20:33:10 UTC 2016 - toddrme2...@gmail.com
+
+- Improve README.packaging.
+
+-------------------------------------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ README.packaging ++++++
--- /var/tmp/diff_new_pack.7W4pl9/_old 2016-10-18 10:37:08.000000000 +0200
+++ /var/tmp/diff_new_pack.7W4pl9/_new 2016-10-18 10:37:08.000000000 +0200
@@ -30,6 +30,7 @@
tag as the currently-supported version of the llvmX_Y
package.
+
===========================================
PATCH-LEVEL UPDATES TO CURRENT LLVM VERSION
@@ -38,10 +39,19 @@
1. llvmX_Y package:
1. Add the new sources to the package and delete the old
- ones
- 2. Update the "Version" tag in llvmX_Y.spec and
+ ones. This will not include cfe-docs-X.Y.Z.src.tar.xz
+ or llvm-docs-X.Y.Z.src.tar.xz (see next item).
+ 2. Build cfe-docs-X.Y.Z.src.tar.xz and
+ llvm-docs-X.Y.Z.src.tar.xz. The instructions are in
+ the %install sectionf of llvmX_Y.spec. The version
+ numbers in the instructions will need to be updated
+ first. Add those sources as well and delete the old
+ ones.
+ 3. Update the "Version" tag in llvmX_Y.spec and
lldbX_Y.spec to match the new sources.
- 3. Update the "_revsn" tag in llvmX_Y.spec and
+ 4. Update the version number in the patches to match the
+ new sources.
+ 5. Update the "_revsn" tag in llvmX_Y.spec and
lldbX_Y.spec to match the revision number of the
tag. This can be found on
http://lists.llvm.org/pipermail/llvm-branch-commits
@@ -49,13 +59,16 @@
"Creating release candidate final" in the subject
line. You want to find the one for the current LLVM
release.
- 4. Update the "_relver" tag in llvmX_Y.spec to match
+ 6. Update the "_relver" tag in llvmX_Y.spec to match
the "Version" tag.
- 5. Confirm everything builds successfully and there are
+ 7. Confirm everything builds successfully and there are
no new rpmlint issues.
+ 8. Update the llvmX_Y.changes and lldbX_Y.changes files.
2. llvm package:
1. Update the "Version" tag to match the new llvmX_Y
version.
+ 2. Update the llvm.changes file.
+
========================================
PATCH-LEVEL UPDATES TO OLD LLVM VERSIONS
@@ -66,10 +79,19 @@
1. llvmX_Y package:
1. Add the new sources to the package and delete the old
- ones
- 2. Update the "Version" tag in llvmX_Y.spec and
+ ones. This will not include cfe-docs-X.Y.Z.src.tar.xz
+ or llvm-docs-X.Y.Z.src.tar.xz (see next item).
+ 2. Build cfe-docs-X.Y.Z.src.tar.xz and
+ llvm-docs-X.Y.Z.src.tar.xz. The instructions are in
+ the %install sectionf of llvmX_Y.spec. The version
+ numbers in the instructions will need to be updated
+ first. Add those sources as well and delete the old
+ ones.
+ 3. Update the "Version" tag in llvmX_Y.spec and
lldbX_Y.spec to match the new sources.
- 3. Update the "_revsn" tag in llvmX_Y.spec and
+ 4. Update the version number in the patches to match the
+ new sources.
+ 5. Update the "_revsn" tag in llvmX_Y.spec and
lldbX_Y.spec to match the revision number of the
tag. This can be found on
http://lists.llvm.org/pipermail/llvm-branch-commits
@@ -77,10 +99,12 @@
"Creating release candidate final" in the subject
line. You want to find the one for the current LLVM
release.
- 4. Update the "_relver" tag in llvmX_Y.spec to match
+ 6. Update the "_relver" tag in llvmX_Y.spec to match
the "Version" tag.
- 5. Confirm everything builds successfully and there are
- no new rpmlint issues.
+ 7. Confirm everything builds successfully and there are
+ no new rpmlint issues. Some patches may need to be
+ removed or rebased.
+ 8. Update the llvmX_Y.changes and lldbX_Y.changes files.
===============================
@@ -94,46 +118,61 @@
1. New llvmX_Y package:
1. Copy (do not link) the old llvmX_Y to the new
major/minor version number.
- 2. Rename the .spec, .changes, and rpmlintrc files in the
+ 2. Add the new sources to the package and delete the old
+ ones. This will not include cfe-docs-X.Y.Z.src.tar.xz
+ or llvm-docs-X.Y.Z.src.tar.xz (see next item).
+ 3. Build cfe-docs-X.Y.Z.src.tar.xz and
+ llvm-docs-X.Y.Z.src.tar.xz. The instructions are in
+ the %install sectionf of llvmX_Y.spec. The version
+ numbers in the instructions will need to be updated
+ first. Add those sources as well and delete the old
+ ones.
+ 4. Rename the .spec, .changes, and rpmlintrc files in the
new llvmX_Y package to the new major/minor version
number
- 3. Rename the base llvm and lldb package in their
+ 5. Rename the base llvm and lldb package in their
respective .spec files to match the new package name.
- 4. Change the "_sonum" tag in llvmX_Y.spec and
+ 6. Change the "_sonum" tag in llvmX_Y.spec and
lldbX_Y.spec to match the new major/minor versions.
It should be of the form "X" if if the "X" minor
version is 0 or "X_Y" if theminor version is greater
than 0.
- 5. Change the "_minor" tag in llvmX_Y.spec to match
+ 7. Change the "_minor" tag in llvmX_Y.spec to match
the new major/minor versions. It should be of the
- form "X.Y".
- 6. Update the "Version", "_revsn", and "_relver" tags
- as described in PATCH-LEVEL UPDATES above.
- 7. Confirm llvmX_Y.spec builds successfully and there are
+ form "X.Y".
+ 8. Change the "_uaver" tag in llvmX_Y.spec and
+ lldb3_8.spec to match the new major/minor versions.
+ It should be of the form "XYY", where "YY" is the
+ two-digit minor version. If the minor version is one
+ digit, put a "0" at the beginning. So "3.8" becomes
+ "308", while "3.10" becomes "310".
+ 9. Update the "Version", "_revsn", and "_relver" tags
+ and the version numbers in the patches as described in
+ PATCH-LEVEL UPDATES above.
+ 10. Confirm llvmX_Y.spec builds successfully and there are
no new rpmlint issues.
- 8. Check whether the .so number of "libc++.so.W.V" has
+ 11. Check whether the .so number of "libc++.so.W.V" has
changed. If so, change "_socxx" tag to match.
It should be of the form "W" if the "V" value is 0
or "W_V" if the "V" value is greater than 0.
- 9. Confirm everything builds successfully and there are
- no new rpmlint issues.
+ 12. Confirm everything builds successfully and there are
+ no new rpmlint issues. Some patches may need to be
+ removed or rebased.
+ 13. Update the llvmX_Y.changes and lldbX_Y.changes files.
2. Old llvmX_Y package:
1. If the .so number of libc++.so.W.V has not changed,
remove the "%if" and %ifarch" tests around
%bcond_without/%bcond_with libcxx in llvmX_Y.spec
and make it always %bcond_with. If the .so numbers
have changed, these can be left-as-is.
- 2. Remove the "%if" and %ifarch" tests around
- %bcond_without/%bcond_with libomp in llvmX_Y.spec
- and make it always %bcond_with.
3. Change "%bcond_without pyclang" to
"%bcond_with pyclang" in llvmX_Y.spec.
- 4. Change BuildRequires "llvm%{_sonum}-gold = %{version}"
- to "llvm-gold" in lldbX_Y.spec.
- 5. Confirm everything builds successfully and there are
+ 4. Confirm everything builds successfully and there are
no new rpmlint issues.
+ 5. Update the llvmX_Y.changes and lldbX_Y.changes files.
3. llvm package:
1. update the "Version" tag to match the new llvmX_Y
version.
2. Change the "_sonum" tag to match the one in the
new "llvmX_Y.spec" and "lldbX_Y.spec" files.
+ 3. Update the llvmX_Y.changes and lldbX_Y.changes files.
