Jerry James kirjoitti 19.11.2021 klo 23.49:
To help those who may be new to packaging, I have started documenting some
of my workflows. I have a set of web pages rooted here:
https://jamezone.org/pleasure/software/Fedora/packager/
Those pages contain walk-throughs and examples illustrating how I approach
various tasks. I'm willing to donate any of that content to Fedora, so if
you see something you think should be on docs.fedoraproject.org, feel free
to tell me so. Also feel free to suggest additions or changes to what I
have there.
That is a great site, with lots of great material that could well be in
the Package Maintainer Docs. My comments here:
Determine the package license: This page could be imported to the Docs
as it is. The only thing I would change it to avoid trying to explaing
the correct content of License: or %license. The authoritative source
for those rules is elsewhere, better just link there. If the
authoritative source is unclear, that should be improved. It is
confusing and error prone to try to explain the same thing in multiple
places that will inevitably drift apart.
Case studies: These would also nicely supplement the current Packaging
Tutorial: GNU Hello [1]. Perhaps some duplication could be removed by
ordering these tutorials, then being very concise about topics that have
already been covered in earlier tutorials. Also, my vision of the
Package Maintainer Docs is that as few tools as possible need to be
invoked. In particular, this means that everything that can be done with
fedpkg, is done with fedpkg. So I would prefer to replace direct calls
to rpmbuild, mock and rpmlint with 'fedpkg mockbuild' and 'fedpkg lint',
and only resort to lower level tooling when 'fedpkg' cannot handle
something.
Build packages with mock: Good material I have not seen elsewhere. Mock
documentation for Fedora Packagers is not in good shape at the moment
[2], it seems that making it good will need quite a bit of work.
Import a new package: This link is broken.
Update a Fedora Package: ABI Compatibility check instructions look like
it would be useful in the Package Maintainer Docs. As for the content,
it is not just good manners to announce abi breaks on devel, but
according to Updates Policy, something that MUST be done.
Use a side tag: Guidance for debugging failing builds locally would be
useful in the Package Maintainer Docs, too. Unfortunately multi-build
docs are in bad shape [3]. I suppose the new material could first be
added somewhere in the docs, then reorganized with all the other
material when that eventually happens.
[1]:
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/
[2]: https://pagure.io/fedora-docs/package-maintainer-docs/issue/44
[3]: https://pagure.io/fedora-docs/package-maintainer-docs/issue/33
Otto
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
