From Fedora Project Wiki
| Line 30: | Line 30: | ||
* Create an archive file of the feature then add it to the '''SOURCES''' in RPM project. | * Create an archive file of the feature then add it to the '''SOURCES''' in RPM project. | ||
: you may need to add that to the '''%prep''' in .spec file. | : you may need to add that to the '''%prep''' in .spec file. | ||
* fill the information for feature template... | |||
Revision as of 21:34, 7 June 2011
References
- Eclipse-fedorapackager-project on fedorahosted
- Eclipse Plugins Packaging
- Packaging references list
- Maximum RPM
- Package_Source_Control
- Eclipse_Fedora_Packager_User_Guide
- Package Maintainers
- Join_the_package_collection_maintainers
- Eclipse_How_to_Maintain_Fedora_Package_User_Guide
- New_package_process_for_existing_contributors
- ReviewGuidelines
- Alex Kurtakov packages
Case Study
- Review-Request Mylyn-context - Mylyn - build (Severin Gehwolf)
- new package SCM request
- git
- Alex Kurtakov packages
Mercurial Eclipse
- Clone the source from javaforge using
hg clone http://javaforge.com:8000/hgeclipse - Create an archive of the latest release source: how to create an archive of a specific tag in mercurial
hg archive -r RELEASE_1.8.1 --type=tar ../mercurialeclipse_1-8-1.tar.bz2
- Create a new feature in Eclipse using New -> feature
- type mercurialeclipse-feature
- change the featureID to com.vectrace.mercurialeclipse (the plug-in needed for this feature)
- Add this feature id to %build in .spec file in -f option
- Don't need to add -d (dependencies) for now, until it complains
- Create an archive file of the feature then add it to the SOURCES in RPM project.
- you may need to add that to the %prep in .spec file.
- fill the information for feature template...