Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document ways to declare sources and patches #3405

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

oturpe
Copy link
Contributor

@oturpe oturpe commented Oct 27, 2024

Fixes #3384

This was written from the perspective of reference manual reader, i.e. trying to document how all the things actual work together. Since various combinations, while possible, do not make much sense, some "X is not recommended" clauses are included. Please instruct if those are not in line with actual recommendations from the RPM team.

@oturpe oturpe requested a review from a team as a code owner October 27, 2024 21:07
@oturpe oturpe requested review from dmnks and removed request for a team October 27, 2024 21:07
@@ -472,6 +481,18 @@ software).

### Sub-sections

#### `%sourcelist`

List of sources, one per row. Handled like unnumbered Source tags. For
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd use "line" instead of "row" here, just to be consistent with the rest of the file.


#### `%patchlist`

List of patches, one per row. Handled like unnumbered Patch tags. For
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

@@ -170,17 +170,26 @@ Short (< 70 characters) summary of the package.

Used to declare source(s) used to build the package. All sources will
will be packaged into source rpms.
Arbitrary number of sources may be declared, for example:
Arbitrary number of sources may be declared. A numbered source is
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep the numbered syntax as the recommended, happy-path style here, and only mention the fact that unnumbered declarations are also possible in a separate paragraph below the examples.

I also don't like mixing the numbered and unnumbered styles in the examples. It makes the syntax look more complicated than it really is.

@dmnks
Copy link
Contributor

dmnks commented Nov 11, 2024

Also, @oturpe, sorry for the late response here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document all the ways to declare source and patch files
2 participants