From Fedora Project Wiki
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
=== Naming === | === Naming === | ||
* For the newly created package, check if it exists in Fedora | * For the newly created package, check if it exists in Fedora Debian or openSuSE packaging directories, and consider to align the package name with them. It helps users. | ||
** 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] | ||
| Line 14: | Line 13: | ||
== Tips == | == Tips == | ||
* For the newly created package, check if it exists on [https://apps.fedoraproject.org/packages/ Fedora Packages], [https://copr.fedorainfracloud.org/coprs/ Fedora Copr], [https://fedoraproject.org/PackageReviewStatus/ Review Status], or [https://fedoraproject.org/wiki/Deprecated_packages Deprecated Packages]. You can judge if you create or revive your package. | |||
* You might see some clues to apply a patch to support ARM on [https://gitlab.com/arm-hpc/packages/-/wikis/home ARM HPC Users Group packages Wiki page]. | |||
* For [https://fedoraproject.org/wiki/Package_Review_Process#Review_Process Review Process - Review swaps], mailing to the medical-sig mailing list might help you. | * For [https://fedoraproject.org/wiki/Package_Review_Process#Review_Process 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 [https://fedoraproject.org/wiki/SIGs/Medical#Fedora_medical_packages_by_category the category list]. | * 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 [https://fedoraproject.org/wiki/SIGs/Medical#Fedora_medical_packages_by_category the category list]. | ||
Latest revision as of 08:08, 28 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 Debian or openSuSE packaging directories, and consider to align the package name with them. It helps users.
- Debian: Debian - Search package directories, Debian Med Packages
- openSuSE: openSuSE - Search packages
Tips
- For the newly created package, check if it exists on Fedora Packages, Fedora Copr, Review Status, or Deprecated Packages. You can judge if you create or revive your package.
- You might see some clues to apply a patch to support ARM on ARM HPC Users Group packages Wiki page.
- 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.