User:Jaffa/mud design

With the new extras process, mud-builder should be re-focused[1] and re-invigorated to help packaging in accordance with the Maemo Packaging Policy[2] 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 

mud create http://packages.ubuntu.com/source/hardy/libgee
mud create http://download.gnome.org/sources/vala/0.3/vala-0.3.4.tar.bz2
mud build libgee
mud upload libgee(*.changes)?

Workflow

TBC

Internals

Awaiting consensus on usage.

Install steps

  1. Ensure mmap given permission in host OS: 
echo 4096 | sudo tee /proc/sys/vm/mmap_min_addr
  1. Add extras and extras-devel to /etc/apt/sources.list.d in Scratchbox
  2. Install mud: 
apt-get install mud
  1. Create ~/.mudrc containing garage username and gnupg key to use
Retrieved from "http://wiki.maemo.org/User:Jaffa/mud_design"