https://bugzilla.redhat.com/show_bug.cgi?id=2388375



--- Comment #10 from Akiyoshi Kurita <[email protected]> ---
Thanks for the detailed review, Cristian.

- I’ve consolidated everything into a single repository and updated the spec
file to use GitHub raw sources for easier review:
  - Spec file (raw):
https://github.com/redadmin-k/gshogi-fedora44/raw/refs/heads/main/gshogi.spec
  - SRPM:
https://github.com/redadmin-k/gshogi-fedora44/raw/refs/heads/main/gshogi-0.1-1.fc44.src.rpm

- Source0 now points to the upstream GitHub tarball (tagged commit).
- Switched to pyproject macros as recommended by the Python packaging
guidelines.
- Fixed Version/Release fields to match the upstream.
- License is now set to GPL-3.0-or-later according to upstream’s LICENSE file.
- Improved the Summary and Description as suggested.
- Clarified the relationship with gnushogi:  
  gshogi is a GTK front-end for the gnushogi engine; it provides a
user-friendly GUI in contrast to the CLI provided by gnushogi itself. (Note:
Debian only packages the engine, not this GUI. I’ve kept `Requires: gnushogi`
accordingly.)

If you have further suggestions, I’m happy to join the #devel chat for a
synchronous discussion.

Thank you for your time and help!


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2388375

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202388375%23c10

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to