Skip to content

guidelines: drop Usage of Periods in Various Package Fields guideline #219

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.

Sign up for GitHub

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

Merged
GildedRoach merged 1 commit into from
Nov 2, 2026
Merged

guidelines: drop Usage of Periods in Various Package Fields guideline #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions src/content/docs/contributing/guidelines.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -628,9 +628,6 @@ BuildRequires: desktop-file-utils
%{_appsdir}/NeoHtop.desktop
```

### Usage of Periods in Various Package Fields
You MUST NOT have a period at the end of any <Code code={`Summary:`} lang={RPMSpec} inline /> tags, and you SHOULD have a period at the end of all <Code code={`%description`} lang={RPMSpec} inline />s.

### Usage of %elifarch

To make specs easier to read, you SHOULD use <Code code={`%ifarch`} lang={RPMSpec} inline /> followed by <Code code={`%elifarch`} lang={RPMSpec} inline /> before <Code code={`%endif`} lang={RPMSpec} inline /> in specs where build steps are arch dependent.
Expand Down
Loading