Talk:New package process for existing contributors

From FedoraProject

Jump to: navigation, search

Re: Step 2: Make a package

An extra step could be included here between steps 2 and 3 which might help the package reviewers. New users could be guided to test their building first as scratch build on Koji before submitting their packages for review.

From https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Install_the_Client_Tools_.28Koji.29

You can now use "koji" to try to build your RPM packages on platforms (e.g., PPC) or distributions don't have.  Note that you can test out builds ("scratch" builds) even when your package hasn't been approved and you don't have a sponsor.  A simple way to do a scratch build using koji is to do this at the command line:
 koji build --arch-override=PLATFORM --scratch TARGET path_to_source_RPM
Where:
* TARGET is a distribution keyword such as dist-f9 (for Fedora 9).  You can run "koji list-targets" to see all targets.  To build for the next release (rawhide), ''don't'' use "dist-rawhide" - use "dist-fX" where X is one more than the current release.
* PLATFORM is a platform keyword such as i386 (32-bit), x86_64, ppc, or ppc64. You can omit --arch-override=PLATFORM, in which case koji will do test builds on all the architectures the spec file says the package supports.
* Note that you need to supply the ''path'' to the source RPM (which ends in .src.rpm), and '''not''' a URL.  (If you only have the spec file, use rpmbuild -bs SPECFILE to create the new source RPM).

--Edwintb 15:34, 6 May 2009 (UTC)

Re: Step 10: You can now import the package to your branches too

The quickest way to do this is to copy the sources file, .spec file
and any patches from devel/ to each branch. Also check if the Makefile
exists and copy it if necessary. After that, cvs add all copied files
and commit them with: cvs commit

Could I just cvs-import the same source into the additional branches ? It does seem to work: Patches get added and committed, the sources are compared to lookaside and not uploaded again, the tag is created. The only thing left to do is make build from within each branch.

Any reason to not do that and instead manually copy around files, cvs add them, commit, which definitely seems more difficult and potential prone to error ? --sunset06 13:52, 13 March 2009 (UTC)