User:Jaffa/mud design

m (Refocusing mud)
m (Add requirements)
Line 1: Line 1:
With the new [[Extras repository process definition|extras process]], [http://mud-builder-garage.maemo.org/ mud-builder] should be re-focused and re-invigorated to help packaging in accordance with the Maemo Packaging Policy[https://maemo.org/forrest-images/pdf/maemo-policy.pdf] and [[Uploading_to_extras]].
With the new [[Extras repository process definition|extras process]], [http://mud-builder-garage.maemo.org/ mud-builder] should be re-focused and re-invigorated to help packaging in accordance with the Maemo Packaging Policy[https://maemo.org/forrest-images/pdf/maemo-policy.pdf] and [[Uploading_to_extras]].
 +
 +
== Requirements ==
 +
* Any package patched, or not from a existing deb source, needs to have a ''maemo'' version suffix.
 +
** For example, if the base version is 7.0, the package version from mud should be 7.0-0maemo1 for the first upload, 7.0-0maemo2 for the second, etc.
 +
** If the upstream package comes from Debian (with version 3.5-7) and is unpatched, the package uploaded from mud is also 3.5-7.
 +
** If the upstream package comes from Debian (with version 3.5-7) and ''is'' patched, the package uploaded from mud is 3.5-7maemo1 for the first upload, 3.5-7maemo2 for the second, etc.
 +
* Warnings should be given when uploading a package with "Section: user/(.*)" where $1 is not in the accepted list.
 +
* It is an error to try and upload a package with no description.
 +
* Auto-sign & upload to ...-extras-builder in one-step
 +
** Use scp to upload all the files, uploading .changes and .dsc ''last'', to avoid auto-builder issues (driven by .dsc files)
== Examples ==
== Examples ==

Revision as of 08:29, 29 June 2008

With the new extras process, mud-builder should be re-focused and re-invigorated to help packaging in accordance with the Maemo Packaging Policy[1] and Uploading_to_extras.

Contents

Requirements

  • Any package patched, or not from a existing deb source, needs to have a maemo version suffix.
    • For example, if the base version is 7.0, the package version from mud should be 7.0-0maemo1 for the first upload, 7.0-0maemo2 for the second, etc.
    • If the upstream package comes from Debian (with version 3.5-7) and is unpatched, the package uploaded from mud is also 3.5-7.
    • If the upstream package comes from Debian (with version 3.5-7) and is patched, the package uploaded from mud is 3.5-7maemo1 for the first upload, 3.5-7maemo2 for the second, etc.
  • Warnings should be given when uploading a package with "Section: user/(.*)" where $1 is not in the accepted list.
  • It is an error to try and upload a package with no description.
  • Auto-sign & upload to ...-extras-builder in one-step
    • Use scp to upload all the files, uploading .changes and .dsc last, to avoid auto-builder issues (driven by .dsc files)

Examples

TBC

Workflow

TBC

Internals

Awaiting consensus on usage.