- Modernize the spec file templates
- Describe all current emacs variants
- Recommend building with emacs-nw
- Guard against %{_emacs_version} being undefined
- Update location of emacs RPM macro file
- Change British English spelling to American English spelling
- Add semantic line breaks
There was some evidence how we should follow for the font package naming
but it was dropped by 20983f3643 and
the reference became a dead link since then.
This isn't good thing because we are missing the reason why fonts-rpm-macros
behave like that. We still need an evidence in our policy.
It has been possible to package NGINX modules for a few cycles
now and a few packages exist in the distribution. This documents
the pattern being used there.
Motivated by the "httpd, pam, and SDL" section having broken formatting
due to the `_` not being escaped. In fixing that, I took the opportunity
to normalize the formatting of other symbols on this page too.
The sections were in a sort of random order; some were alphabetical and
some weren't. Sort them all except for the odd "httpd, pam and SDL"
section.
Also consistently capitalize section titles.
The linkchecker tool was used to identify broken links in the generated
documentation. After running 'make && make serve' in one terminal,
linkchecker is run in another:
linkchecker --check-extern --user-agent="curl/7.61.1" \
--ignore-url="file:///antora/" \
--ignore-url="https://crates.io" \
--ignore-url="https://hosting-service/" \
http://0.0.0.0:8000/packaging-guidelines/
One broken link remains: the Perl SIG "New Package SCM Request" link.
This has no direct replacement (in the context of adding an 'initial-cc'
to bug reports), as far as I can tell. That text and link need to be
rewritten. In context:
New Perl packages should set the
https://lists.fedoraproject.org/admin/lists/perl-devel.lists.fedoraproject.org/[Fedora
Perl SIG mailing list] as a member of the initial-cc list for bugzilla.
This can be done by adding the user `+perl-sig+` to the initial CC list
when creating the link:Package_SCM_admin_requests#New_Packages[New Package
SCM Request].
We ignore https://crates.io because it behaves badly with non-browser
tools (refer to https://github.com/rust-lang/crates.io/issues/788 for
details).
The --user-agent option is necessary to work around issues at sites like
drupal.org, which return a 403 when used with linkchecker's default
User-Agent header (LinkChecker/X.Y).
