From Fedora Project Wiki
(New page: = Guidelines for submitting a new package to MinGW = Help the reviewers by following these straightforward steps: # Join the package maintainers # and in part...)
 
 
Line 6: Line 6:
# and in particular, [[PackageMaintainers/Join#Create_Your_Review_Request|create a review request]] for your package.
# and in particular, [[PackageMaintainers/Join#Create_Your_Review_Request|create a review request]] for your package.
# Make a scratch build of your package: <br> <code>koji build --scratch dist-f11 <i>your.src.rpm</i></code>
# Make a scratch build of your package: <br> <code>koji build --scratch dist-f11 <i>your.src.rpm</i></code>
# Post a link in the review request
# and post a link to the scratch build in the review request.
# Run rpmlint on the source and binary RPMs and attach the full output to the review request
# Run rpmlint on the source and binary RPMs and attach the full output to the review request
# Add [https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw fedora-mingw@lists.fedoraproject.org] to the CC list for the review request
# Add [https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw fedora-mingw@lists.fedoraproject.org] to the CC list for the review request
# Make the review request alias field be the same as the package name (this makes it easy to refer to the package by name)
# Make the review request alias field be the same as the package name (this makes it easy to refer to the package by name)
# Set the dependencies in the review request correctly.  Almost every package should depend on <code>mingw32-gcc</code>.
# Set the dependencies in the review request correctly.  Almost every package should depend on <code>[https://bugzilla.redhat.com/show_bug.cgi?id=mingw32-gcc mingw32-gcc]</code>.
 
Here is an example review request:
 
https://bugzilla.redhat.com/show_bug.cgi?id=491317

Latest revision as of 13:48, 20 March 2009

Guidelines for submitting a new package to MinGW

Help the reviewers by following these straightforward steps:

  1. Join the package maintainers
  2. and in particular, create a review request for your package.
  3. Make a scratch build of your package:
    koji build --scratch dist-f11 your.src.rpm
  4. and post a link to the scratch build in the review request.
  5. Run rpmlint on the source and binary RPMs and attach the full output to the review request
  6. Add fedora-mingw@lists.fedoraproject.org to the CC list for the review request
  7. Make the review request alias field be the same as the package name (this makes it easy to refer to the package by name)
  8. Set the dependencies in the review request correctly. Almost every package should depend on mingw32-gcc.

Here is an example review request:

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