Task:Mer Repository Setup

(→Builder specifics)
(→Builder specifics)
Line 33: Line 33:
**sb-conf install MER-ARMEL --etc --devkits
**sb-conf install MER-ARMEL --etc --devkits
*For i386 a following model could work:
*For i386 a following model could work:
-
**A tar.gz with debootstrap of a buildd variant
+
**A tar.gz with debootstrap of a buildd variant (found at http://stskeeps.subnetmask.net/mer/mer-i386-rootstrap-v0.tar.gz ) , apt sources may have to be adjusted.
-
**chrooting into the unpacked tar.gz, put in source package, grab dependancies, build it natively.
+
**chrooting into the unpacked tar.gz, put in source package, grab dependancies, build it natively (pbuilder?)

Revision as of 21:47, 22 December 2008

As part of the Mer bootstrapping process, a repository at http://repository.maemo.org/community/ will have to be set up.

Contents

Repository layout

  • Suite: unstable
  • Codename: alpha
  • Components: main
  • Architectures: i386 armel (all)

(later we will have a stable distribution, and a similar promotion interface to extras one will be used)

Bootstrapping

  • Copying all .dsc and .deb from repository.mer.tspre.org and loading into repository. We get SDK problems if we have to re-compile everything again, and the packages were built natively already.

Upload possibilities

  • Similar interface as to uploading to i386 & armel builder as with extras.
  • There should be a specific moderation of invitations to be able to upload to the Mer repositories.
  • There should be a possibility to upload self-built packages (source & binary packages), like 'non-free' but directly to 'main', for certain uploaders (kernel-diablo is a specific problem, as it doesn't build cleanly on new SDK with gcc4)

Builder specifics

Retrieved from "https://wiki.maemo.org/Task:Mer_Repository_Setup"