From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
=== Naming === | === Naming === | ||
* For the newly created package, check if it exists in Debian or openSuSE packaging directories, and consider to align the package name with them. It helps users. | * For the newly created package, check if it exists in Fedora Copr, Debian or openSuSE packaging directories, and consider to align the package name with them. It helps users. | ||
** Fedora Copr: [https://copr.fedorainfracloud.org/coprs/ - Search projects by (package) name] | |||
** Debian: [https://www.debian.org/distrib/packages Debian - Search package directories], [https://blends.debian.org/med/tasks/ Debian Med Packages] | ** Debian: [https://www.debian.org/distrib/packages Debian - Search package directories], [https://blends.debian.org/med/tasks/ Debian Med Packages] | ||
** openSuSE: [https://software.opensuse.org/ openSuSE - Search packages] | ** openSuSE: [https://software.opensuse.org/ openSuSE - Search packages] | ||
Revision as of 20:56, 27 April 2020
This page is Fedora Medical SIG's packaging guidelines page. Please discuss in the medical-sig mailing list to update this page for your ideas.
Fedora Packaging Guidelines for Medical
Follow the common Fedora Packaging Guidelines. In this page, we note the Medical specific topics.
Naming
- For the newly created package, check if it exists in Fedora Copr, Debian or openSuSE packaging directories, and consider to align the package name with them. It helps users.
- Fedora Copr: - Search projects by (package) name
- Debian: Debian - Search package directories, Debian Med Packages
- openSuSE: openSuSE - Search packages
Tips
- For Review Process - Review swaps, mailing to the medical-sig mailing list might help you.
- After you have a git repository for your package and build your package, please consider to announce it at the medical-sig mailing list and enable Koschei (example: https://koschei.fedoraproject.org/package/bwa - Scheduler parameters - Tracked by Koschei: True). Then the package is tagged by someone as a proper category in Koschei, and managed on the category list.