From dc86e6597542d3804dcfbd2a0acc8e17b5afc364 Mon Sep 17 00:00:00 2001 From: Tomas Juhasz Date: Dec 30 2024 12:43:57 +0000 Subject: [PATCH 1/4] Update modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc Added a short step by step guide how to use Corp for new contributors --- diff --git a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc index 3a849ff..af610fa 100644 --- a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc +++ b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc @@ -57,12 +57,38 @@ not hidden behind some service that makes people wait to download things or redirects through advertising pages. -If you want to make ad-hoc builds available for users -while you are getting the package into the official repositories, -consider using https://copr.fedorainfracloud.org[Copr]. -It is a lightweight automated build system -that can create repositories using the SRPM you upload. -You can use this Copr space to point reviewers to your src.rpm and spec. + +[how_to_make_your_build_available] +== How to make your build available + +If you want to make ad-hoc builds available for users while you are getting the +package into the official repositories, consider using +https://copr.fedorainfracloud.org[Copr]. It is a lightweight automated build +system that can create repositories using the SRPM you upload. You can use this +Copr space to point reviewers to your src.rpm and spec. + +First you need to log to https://copr.fedorainfracloud.org[Copr], you can use +your fedora account. + +Then follow this +https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build +the project. Use the fedora chroot options in setup of the project and in the +provide the source step, provide either srpm created with the scratchbuild +command or the spec file. + +After the build is completed you can use the following links for the review +process: + +* Link to Spec file: + - the file can be found under packages, click the name of your package and + then under general information look for your dist-git repositary. Find the + *Spec* file in this repository and copy it's link, but replace the *tree* + part of the URL with the string *plain*, then use it for the review submission. +* Link to SRPM file: + - the file can be found under builds, click on the id of your last build and + under general information look for link named directory. Here look in to + the */srpm-build/your_build_id/* folder and copy the *src.rpm* file URL for + your review submission. [#create_your_review_request] == Create Your Review Request From 420c35ed225c8b9d8370713d05eeee76a8c5792e Mon Sep 17 00:00:00 2001 From: Tomas Juhasz Date: Dec 30 2024 12:43:57 +0000 Subject: [PATCH 2/4] Update modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc Adjusted with semantic line breaks, I have moved the text introducing copr as an option from section upload your package, but have not changed it's wording or syntax --- diff --git a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc index af610fa..6777065 100644 --- a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc +++ b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc @@ -57,38 +57,42 @@ not hidden behind some service that makes people wait to download things or redirects through advertising pages. - [how_to_make_your_build_available] == How to make your build available - -If you want to make ad-hoc builds available for users while you are getting the -package into the official repositories, consider using -https://copr.fedorainfracloud.org[Copr]. It is a lightweight automated build -system that can create repositories using the SRPM you upload. You can use this -Copr space to point reviewers to your src.rpm and spec. - -First you need to log to https://copr.fedorainfracloud.org[Copr], you can use -your fedora account. - -Then follow this -https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build -the project. Use the fedora chroot options in setup of the project and in the -provide the source step, provide either srpm created with the scratchbuild -command or the spec file. - -After the build is completed you can use the following links for the review -process: + +If you want to make ad-hoc builds available for users +while you are getting the package into the official repositories, +consider using https://copr.fedorainfracloud.org[Copr]. +It is a lightweight automated build system +that can create repositories using the SRPM you upload. +You can use this Copr space to point reviewers to your src.rpm and spec. + +First you need to log to https://copr.fedorainfracloud.org[Copr], +you can use your fedora account. + +Then follow this https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], +to build the project. +Use the fedora chroot options in setup of the project +and in the provide the source step, +provide either srpm created with the scratchbuild command or the spec file. + +After the build is completed +you can use the following links for the review process: * Link to Spec file: - - the file can be found under packages, click the name of your package and - then under general information look for your dist-git repositary. Find the - *Spec* file in this repository and copy it's link, but replace the *tree* - part of the URL with the string *plain*, then use it for the review submission. +the file can be found under your copr packages, +click the name of your package +and then under general information look for your dist-git repositary. +Find the *Spec* file in this repository tree and copy it's link, +but replace the *tree* part of the URL with the string *plain*, +then use it for the review submission. + * Link to SRPM file: - - the file can be found under builds, click on the id of your last build and - under general information look for link named directory. Here look in to - the */srpm-build/your_build_id/* folder and copy the *src.rpm* file URL for - your review submission. +the file can be found under your copr builds, +click on the *id* of your last successful build +and under general information look for link named directory. +Here look in to the */srpm-build/your_build_id/* folder +and copy the *src.rpm* file URL for your review submission. [#create_your_review_request] == Create Your Review Request From 1caa4fe876a4b1564be8ba6505f70ec477695780 Mon Sep 17 00:00:00 2001 From: Tomas Juhasz Date: Dec 30 2024 12:43:57 +0000 Subject: [PATCH 3/4] Update modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc Slightly changed the writing of the upload the source section --- diff --git a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc index 6777065..84e16f9 100644 --- a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc +++ b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc @@ -72,9 +72,20 @@ you can use your fedora account. Then follow this https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build the project. -Use the fedora chroot options in setup of the project -and in the provide the source step, -provide either srpm created with the scratchbuild command or the spec file. +During the built step you need to upload your source, +you can choose the one which works for you the best, +but if you don't have the source uploaded somewhere else, +you can select the Upload option +and then in the provide the step section, +click on Browse... button to select a file. +Now in the next section you need to specify the Chroots +and other built options, +select all fedora variations +and adjust other settings as necessary. + +After the build is completed +you can use the following links for the review process: + After the build is completed you can use the following links for the review process: From 6ade090e4919c8c2075bf288a3539012421bc1b0 Mon Sep 17 00:00:00 2001 From: Tomas Juhasz Date: Dec 30 2024 12:43:57 +0000 Subject: [PATCH 4/4] Update modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc Adjusted the contribution based on suggestions in the comments --- diff --git a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc index 84e16f9..90d3a41 100644 --- a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc +++ b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc @@ -56,31 +56,29 @@ but it is important that the files be directly accessible, not hidden behind some service that makes people wait to download things or redirects through advertising pages. - -[how_to_make_your_build_available] -== How to make your build available If you want to make ad-hoc builds available for users while you are getting the package into the official repositories, -consider using https://copr.fedorainfracloud.org[Copr]. -It is a lightweight automated build system -that can create repositories using the SRPM you upload. -You can use this Copr space to point reviewers to your src.rpm and spec. +consider using the recommended approach with https://copr.fedorainfracloud.org[Copr]. +It allows creating repositories using the src.rpm or spec file, +which can be then shared with the reviewers. +It also can create automatic builds from these files +and distribute the results. First you need to log to https://copr.fedorainfracloud.org[Copr], -you can use your fedora account. +you can use your Fedora account. Then follow this https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build the project. -During the built step you need to upload your source, +During the "New Build" step you need to upload your source, you can choose the one which works for you the best, but if you don't have the source uploaded somewhere else, -you can select the Upload option +you can select the _Upload_ option and then in the provide the step section, -click on Browse... button to select a file. +click on _Browse..._ button to select a file. Now in the next section you need to specify the Chroots and other built options, -select all fedora variations +select atleast one fedora-rawhide chroot and adjust other settings as necessary. After the build is completed @@ -91,7 +89,7 @@ After the build is completed you can use the following links for the review process: * Link to Spec file: -the file can be found under your copr packages, +go to your copr packages, click the name of your package and then under general information look for your dist-git repositary. Find the *Spec* file in this repository tree and copy it's link, @@ -99,7 +97,7 @@ but replace the *tree* part of the URL with the string *plain*, then use it for the review submission. * Link to SRPM file: -the file can be found under your copr builds, +in your copr builds, click on the *id* of your last successful build and under general information look for link named directory. Here look in to the */srpm-build/your_build_id/* folder