[why] pkgbuild_repo field's parameter format is not uniform for different git repository. Novices are easy to make mistakes.
[how] Add examples of three types of git repository used by build-pkg.
Signed-off-by: Lin Jiaxin ljx.joe@qq.com --- jobs/build-pkg.yaml | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/jobs/build-pkg.yaml b/jobs/build-pkg.yaml index 5888838a..b17fd2ad 100644 --- a/jobs/build-pkg.yaml +++ b/jobs/build-pkg.yaml @@ -1,4 +1,9 @@ suite: build-pkg category: functional
+# pkgbuild_repo examples +# pkgbuild_repo: archlinux/aur-j/java8-openjdk +# pkgbuild_repo: archlinux/community//keepalived/trunk +# pkgbuild_repo: archlinux/packages//prometheus-node-exporter/trunk + build-pkg:
On Wed, Oct 28, 2020 at 05:00:37PM +0800, Lin Jiaxin wrote:
[why] pkgbuild_repo field's parameter format is not uniform for different git repository. Novices are easy to make mistakes.
[how] Add examples of three types of git repository used by build-pkg.
Signed-off-by: Lin Jiaxin ljx.joe@qq.com
jobs/build-pkg.yaml | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/jobs/build-pkg.yaml b/jobs/build-pkg.yaml index 5888838a..b17fd2ad 100644 --- a/jobs/build-pkg.yaml +++ b/jobs/build-pkg.yaml @@ -1,4 +1,9 @@ suite: build-pkg category: functional
+# pkgbuild_repo examples +# pkgbuild_repo: archlinux/aur-j/java8-openjdk +# pkgbuild_repo: archlinux/community//keepalived/trunk +# pkgbuild_repo: archlinux/packages//prometheus-node-exporter/trunk
looks good to me.
Thanks, Liushaofei
build-pkg:
2.23.0
On Wed, Oct 28, 2020 at 05:00:37PM +0800, Lin Jiaxin wrote:
[why] pkgbuild_repo field's parameter format is not uniform for different git repository. Novices are easy to make mistakes.
[how] Add examples of three types of git repository used by build-pkg.
Signed-off-by: Lin Jiaxin ljx.joe@qq.com
What's the difference between build-pkg add cci-makepkg? Which one should we use when we want to make a package?
Thanks, Yale
jobs/build-pkg.yaml | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/jobs/build-pkg.yaml b/jobs/build-pkg.yaml index 5888838a..b17fd2ad 100644 --- a/jobs/build-pkg.yaml +++ b/jobs/build-pkg.yaml @@ -1,4 +1,9 @@ suite: build-pkg category: functional
+# pkgbuild_repo examples +# pkgbuild_repo: archlinux/aur-j/java8-openjdk +# pkgbuild_repo: archlinux/community//keepalived/trunk +# pkgbuild_repo: archlinux/packages//prometheus-node-exporter/trunk
build-pkg:
2.23.0
On Thu, Oct 29, 2020 at 10:04:02AM +0800, Zhang Yale wrote:
On Wed, Oct 28, 2020 at 05:00:37PM +0800, Lin Jiaxin wrote:
[why] pkgbuild_repo field's parameter format is not uniform for different git repository. Novices are easy to make mistakes.
[how] Add examples of three types of git repository used by build-pkg.
Signed-off-by: Lin Jiaxin ljx.joe@qq.com
What's the difference between build-pkg add cci-makepkg? Which one should we use when we want to make a package?
Their PKGBUILD source and output are different. cci-makepkg <- lkp-tests/pkg build-pkg <- /srv/git/archlinux <- aur offical web build-pkg has more PKGBUILD.
lkp/tests can't get build-pkg's outputing cgz now. We're remodeling it. So use cci-makepkg first unless you're just trying to verify PKGBUILD's right.
Thanks, Jiaxin
On Thu, Oct 29, 2020 at 10:38:49AM +0800, Lin Jiaxin wrote:
On Thu, Oct 29, 2020 at 10:04:02AM +0800, Zhang Yale wrote:
On Wed, Oct 28, 2020 at 05:00:37PM +0800, Lin Jiaxin wrote:
[why] pkgbuild_repo field's parameter format is not uniform for different git repository. Novices are easy to make mistakes.
[how] Add examples of three types of git repository used by build-pkg.
Signed-off-by: Lin Jiaxin ljx.joe@qq.com
What's the difference between build-pkg add cci-makepkg? Which one should we use when we want to make a package?
Their PKGBUILD source and output are different. cci-makepkg <- lkp-tests/pkg build-pkg <- /srv/git/archlinux <- aur offical web build-pkg has more PKGBUILD.
lkp/tests can't get build-pkg's outputing cgz now. We're remodeling it. So use cci-makepkg first unless you're just trying to verify PKGBUILD's right.
Thanks, Jiaxin
Good! Thanks for your patient explanation.
Thanks, Yale