Compare commits

..

2 Commits

Author SHA1 Message Date
Kevron Rees 1145477b30 Add section to documentation about updating package version
Document includes a description for pumping the release, but what
if there is a completely new upstream version?  This patch adds a
section that describes how to update the upstream url for a
package and update the package information accordingly.

Signed-off-by: Kevron Rees <kevron.m.rees@intel.com>
2018-08-13 10:51:27 -07:00
Kevron Rees 19cb72b28e add link to autospec documentation
Documentation only describes how to tweak autospec behavior by
modifying one file ("buildreq_add").  A new developer might not be
aware that there are several other files that can be modified that
will change autospec behavior.  Link to the autospec documentation
so that developers can learn of the other files and how autospec
uses them.

Signed-off-by: Kevron Rees <kevron.m.rees@intel.com>
2018-08-13 10:51:27 -07:00
+14
View File
@@ -102,6 +102,10 @@ $ echo missing-build-req >> buildreq_add
$ make autospec
```
Please see https://github.com/clearlinux/autospec#common-files for
documention on buildreq_add and the other files autospec uses during the
build process.
### Bump the release number for a package
If you simply need to increment a package's release number and rebuild the
@@ -112,6 +116,16 @@ $ make bump
$ make build
```
### Update the release version for a package
If you have an update release version for a package, you can change the url
for the new release in the package/example-pkg/Makefile. After modifying the
new url, run `make autospec` again to fetch the new package and rebuild.
```
$ make autospec
```
## Other topics
### Customizing the mock config