Changeset 879 for rpmbuild-bot
- Timestamp:
- Oct 31, 2016, 6:07:52 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
rpmbuild-bot/rpmbuild-bot.sh
r867 r879 17 17 # in the same directory to set up the environment and control the build 18 18 # process. The main purpose of this script is to build RPM packages for a 19 # specific distribution channel maintaining distribution-s iecific rules.19 # specific distribution channel maintaining distribution-specific rules. 20 20 # 21 21 # Usage … … 30 30 # .spec is assumed). The spec file is searched in the SPECS directory of the 31 31 # rpmbuild tree (usually $USER/rpmbuild/SPECS, rpmbuild --eval='%_specdir' 32 # will show the exact location). This may be overrid en by giving a spec file32 # will show the exact location). This may be overridden by giving a spec file 33 33 # with a path specification. 34 34 # … … 54 54 # 55 55 # The "build" command will fail if the log directory contains files from a 56 # successful lrun of another "build" command for this package. This is to56 # successful run of another "build" command for this package. This is to 57 57 # prevent overwriting successfully built packages that are not yet uploaded to 58 58 # the distribution repository (see the "upload" command). You should either … … 65 65 # exists, all files in it are assumed to be auxiliary source files used by the 66 66 # .spec file via SourceN: directives. These files will be automatically copied 67 # to the SOURCES directory in the rpmbuild tree bef ure starting the build67 # to the SOURCES directory in the rpmbuild tree before starting the build 68 68 # process. 69 69 # … … 85 85 # 86 86 # prep Execute the %prep section of the spec file only. 87 # build Execute the %build section only (requ res %prep to be executed87 # build Execute the %build section only (requires %prep to be executed 88 88 # before). May be run multiple times. 89 # install Execute the %install sect uion only (requires "prep" and "build"89 # install Execute the %install section only (requires "prep" and "build" 90 90 # to be executed before). May be run multiple times. 91 91 # pack Create the RPM packages (requires "prep", "build" and "install" … … 113 113 # (usually experimental or similar). 114 114 # 115 # The upload command also requires the spec file to be under SVN ve srion control116 # and will try to commit it beforeuploading the RPMs to the repository with the115 # The upload command also requires the spec file to be under SVN version control 116 # and will try to commit it after uploading the RPMs to the repository with the 117 117 # automatic commit message that says "spec: PROJECT: Release version VERSION." 118 118 # (where PROJECT is the spec file name and VERSION is the full version, 119 # excluding the distribution mark, as specified by the spec file). If the commit120 # operation fails, uploading will be aborted. This to ensure that the spec file121 # are published at the same time the RPMs are published - to guarantee their122 # consisnency and simplify further maintenance. Note that the auxiliary source123 # directory named SPEC and located near the spec file (see the "build" command),124 # if it exists, will also be committed.119 # excluding the distribution mark, as specified by the spec file).This to ensure 120 # that the spec file is published at the same time the RPMs are published - to 121 # guarantee their consistency and simplify further maintenance. Note that the 122 # auxiliary source directory named SPEC and located near the spec file (see the 123 # "build" command), if it exists, will also be committed. If the spec file is 124 # not under version control, the "upload" command will fail. 125 125 # 126 126 # Note that the "upload" command needs log files from the "build" command … … 183 183 # 184 184 # Note that the log files from the "build" and "upload" commands are also 185 # removed by this command upon suc essful package removal.185 # removed by this command upon successful package removal. 186 186 # 187 187 # Return value
Note:
See TracChangeset
for help on using the changeset viewer.