pool/llvm
SHA256
4
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Accepting request 433804 from home:TheBlackCat:branches:devel:tools:compiler

Browse Source 
Improve README.packaging.

OBS-URL: https://build.opensuse.org/request/show/433804
OBS-URL: https://build.opensuse.org/package/show/devel:tools:compiler/llvm?expand=0&rev=484
This commit is contained in:
Ismail Dönmez 2016-10-12 07:53:17 +00:00 committed by Git OBS Bridge
parent 8e4aaf97d7
commit 033ae69108
2 changed files with 72 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

95
README.packaging
View File

@ -30,6 +30,7 @@ NOTE: This package should always have the same "License"
tag as the currently-supported version of the llvmX_Y tag as the currently-supported version of the llvmX_Y
package. package.
=========================================== ===========================================
PATCH-LEVEL UPDATES TO CURRENT LLVM VERSION PATCH-LEVEL UPDATES TO CURRENT LLVM VERSION
@ -38,10 +39,19 @@ llvmX_Y package need to be updated.
1. llvmX_Y package: 1. llvmX_Y package:
1. Add the new sources to the package and delete the old 1. Add the new sources to the package and delete the old
ones ones. This will not include cfe-docs-X.Y.Z.src.tar.xz
2. Update the "Version" tag in llvmX_Y.spec and 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. 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 lldbX_Y.spec to match the revision number of the
tag. This can be found on tag. This can be found on
http://lists.llvm.org/pipermail/llvm-branch-commits http://lists.llvm.org/pipermail/llvm-branch-commits
@ -49,13 +59,16 @@ llvmX_Y package need to be updated.
"Creating release candidate final" in the subject "Creating release candidate final" in the subject
line. You want to find the one for the current LLVM line. You want to find the one for the current LLVM
release. 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. the "Version" tag.
5. Confirm everything builds successfully and there are 7. Confirm everything builds successfully and there are
no new rpmlint issues. no new rpmlint issues.
8. Update the llvmX_Y.changes and lldbX_Y.changes files.
2. llvm package: 2. llvm package:
1. Update the "Version" tag to match the new llvmX_Y 1. Update the "Version" tag to match the new llvmX_Y
version. version.
2. Update the llvm.changes file.
======================================== ========================================
PATCH-LEVEL UPDATES TO OLD LLVM VERSIONS PATCH-LEVEL UPDATES TO OLD LLVM VERSIONS
@ -66,10 +79,19 @@ needs to be updated.
1. llvmX_Y package: 1. llvmX_Y package:
1. Add the new sources to the package and delete the old 1. Add the new sources to the package and delete the old
ones ones. This will not include cfe-docs-X.Y.Z.src.tar.xz
2. Update the "Version" tag in llvmX_Y.spec and 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. 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 lldbX_Y.spec to match the revision number of the
tag. This can be found on tag. This can be found on
http://lists.llvm.org/pipermail/llvm-branch-commits http://lists.llvm.org/pipermail/llvm-branch-commits
@ -77,10 +99,12 @@ needs to be updated.
"Creating release candidate final" in the subject "Creating release candidate final" in the subject
line. You want to find the one for the current LLVM line. You want to find the one for the current LLVM
release. 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. the "Version" tag.
5. Confirm everything builds successfully and there are 7. Confirm everything builds successfully and there are
no new rpmlint issues. 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 @@ needs to be modified.
1. New llvmX_Y package: 1. New llvmX_Y package:
1. Copy (do not link) the old llvmX_Y to the new 1. Copy (do not link) the old llvmX_Y to the new
major/minor version number. 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 new llvmX_Y package to the new major/minor version
number 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. 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. lldbX_Y.spec to match the new major/minor versions.
It should be of the form "X" if if the "X" minor It should be of the form "X" if if the "X" minor
version is 0 or "X_Y" if theminor version is greater version is 0 or "X_Y" if theminor version is greater
than 0. 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 the new major/minor versions. It should be of the
form "X.Y". form "X.Y".
6. Update the "Version", "_revsn", and "_relver" tags 8. Change the "_uaver" tag in llvmX_Y.spec and
as described in PATCH-LEVEL UPDATES above. lldb3_8.spec to match the new major/minor versions.
7. Confirm llvmX_Y.spec builds successfully and there are 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. 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. changed. If so, change "_socxx" tag to match.
It should be of the form "W" if the "V" value is 0 It should be of the form "W" if the "V" value is 0
or "W_V" if the "V" value is greater than 0. or "W_V" if the "V" value is greater than 0.
9. Confirm everything builds successfully and there are 12. Confirm everything builds successfully and there are
no new rpmlint issues. 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: 2. Old llvmX_Y package:
1. If the .so number of libc++.so.W.V has not changed, 1. If the .so number of libc++.so.W.V has not changed,
remove the "%if" and %ifarch" tests around remove the "%if" and %ifarch" tests around
%bcond_without/%bcond_with libcxx in llvmX_Y.spec %bcond_without/%bcond_with libcxx in llvmX_Y.spec
and make it always %bcond_with. If the .so numbers and make it always %bcond_with. If the .so numbers
have changed, these can be left-as-is. 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 3. Change "%bcond_without pyclang" to
"%bcond_with pyclang" in llvmX_Y.spec. "%bcond_with pyclang" in llvmX_Y.spec.
4. Change BuildRequires "llvm%{_sonum}-gold = %{version}" 4. Confirm everything builds successfully and there are
to "llvm-gold" in lldbX_Y.spec.
5. Confirm everything builds successfully and there are
no new rpmlint issues. no new rpmlint issues.
5. Update the llvmX_Y.changes and lldbX_Y.changes files.
3. llvm package: 3. llvm package:
1. update the "Version" tag to match the new llvmX_Y 1. update the "Version" tag to match the new llvmX_Y
version. version.
2. Change the "_sonum" tag to match the one in the 2. Change the "_sonum" tag to match the one in the
new "llvmX_Y.spec" and "lldbX_Y.spec" files. new "llvmX_Y.spec" and "lldbX_Y.spec" files.
3. Update the llvmX_Y.changes and lldbX_Y.changes files.

5
llvm.changes
View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Fri Oct 7 20:33:10 UTC 2016 - toddrme2178@gmail.com
- Improve README.packaging.
------------------------------------------------------------------- -------------------------------------------------------------------
Thu Oct 6 07:05:41 UTC 2016 - idonmez@suse.com Thu Oct 6 07:05:41 UTC 2016 - idonmez@suse.com