[main] Identify exemplar package specs and add to ecosystem guidelines #1545

Open
opened 2026-06-15 12:47:25 +00:00 by ankursinha · 1 comment
Member

We received some feedback that while the examples/empty specs in the different programming ecosystem guidelines are useful, examples of actual packages in Fedora would provide more realistic/real-world documentation. We were suggested to:

  • identify a "simple" package, comment its spec verbosely
  • identify a less "simple" package, comment its spec verbosely

Link to these in the guidelines.


We certainly have enough packages to choose from for most ecosystems here, so verbosely commenting a couple to provide real-world examples should be doable.

Thoughts?

We received some feedback that while the examples/empty specs in the different programming ecosystem guidelines are useful, examples of actual packages in Fedora would provide more realistic/real-world documentation. We were suggested to: - identify a "simple" package, comment its spec verbosely - identify a less "simple" package, comment its spec verbosely Link to these in the guidelines. ---- We certainly have enough packages to choose from for most ecosystems here, so verbosely commenting a couple to provide real-world examples should be doable. Thoughts?
Owner

I would guess it's likely that even the better package spec files run into real life enough that they aren't great examples. Also not sure who would have time to go through a lot of the specfiles.

But if you do have time I'd probably start with the packages with binaries in a minimal build, then you could look through them and point out a few you think might be good examples?

I would guess it's likely that even the better package spec files run into real life enough that they aren't great examples. Also not sure who would have time to go through a lot of the specfiles. But if you do have time I'd probably start with the packages with binaries in a minimal build, then you could look through them and point out a few you think might be good examples?
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
packaging/guidelines#1545
No description provided.