Task:Mer Repository Setup - Revision history

imported_>amigadave: {{mer}}

2010-11-12T15:11:08Z

← Older revision		Revision as of 15:11, 12 November 2010
Line 1:		Line 1:
			{{mer}}

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

imported_>twaelti at 18:32, 18 October 2009

2009-10-18T18:32:56Z

← Older revision		Revision as of 18:32, 18 October 2009
Line 35:		Line 35:
	**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.		**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 (pbuilder?)		**chrooting into the unpacked tar.gz, put in source package, grab dependancies, build it natively (pbuilder?)
			[[Category:Tasks]]

84.238.94.136: /* Builder specifics */

2008-12-22T21:47:56Z

Builder specifics

← Older revision		Revision as of 21:47, 22 December 2008
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?)

84.238.94.136: /* Builder specifics */

2008-12-22T20:25:38Z

Builder specifics

← Older revision		Revision as of 20:25, 22 December 2008
Line 32:		Line 32:
	**sb-conf rootstrap MER-ARMEL http://stskeeps.subnetmask.net/mer/mer-armel-rootstrap-v8.tar.gz		**sb-conf rootstrap MER-ARMEL http://stskeeps.subnetmask.net/mer/mer-armel-rootstrap-v8.tar.gz
	**sb-conf install MER-ARMEL --etc --devkits		**sb-conf install MER-ARMEL --etc --devkits
			*For i386 a following model could work:
			**A tar.gz with debootstrap of a buildd variant
			**chrooting into the unpacked tar.gz, put in source package, grab dependancies, build it natively.

84.238.94.136 at 17:49, 22 December 2008

2008-12-22T17:49:49Z

← Older revision		Revision as of 17:49, 22 December 2008
Line 23:		Line 23:

	*Builders should target both i386 and armel (armv5el, not vfp) (will probably have to be set with CFLAGS)		*Builders should target both i386 and armel (armv5el, not vfp) (will probably have to be set with CFLAGS)
	*Mer has a scratchbox v1 SDK ~~(see [~~http://~~wiki.maemo~~.org/~~Mer_Blueprint#SB1_SDK_Guide SB1 SDK Guide]), using~~ scratchbox-toolchain-arm-linux-cs2008q3-72_1.0.8-1_i386.deb, ~~and a~~ rootstrap ~~for~~ armel. ~~i386 rootstrap TBA~~.		*Mer has, for armv5el, a scratchbox v1 SDK:
			**Toolchain: http://scratchbox.org/~jhakala/unofficial/scratchbox-toolchain-arm-linux-cs2008q3-72_1.0.8-1_i386.deb
			**Devkit: http://stskeeps.subnetmask.net/mer/scratchbox-devkit-mer_1.0.8_i386.deb , debian-etch, cputransp
			**On top of QEMU EABI: (http://maemogeek.blogspot.com/2007/11/installing-qemu-arm-eabi-patch-into.html)
			**sb-conf setup MER-ARMEL --compiler=arm-linux-cs2008q3-72 --devkits=debian-etch:cputransp:mer --cputransp=qemu-arm-eabi -f
			**sb-conf reset -f MER-ARMEL
			**sb-conf select MER-ARMEL
			**sb-conf rootstrap MER-ARMEL http://stskeeps.subnetmask.net/mer/mer-armel-rootstrap-v8.tar.gz
			**sb-conf install MER-ARMEL --etc --devkits

imported_>stskeeps at 19:10, 15 December 2008

2008-12-15T19:10:21Z

← Older revision		Revision as of 19:10, 15 December 2008
Line 4:		Line 4:

	*Suite: unstable		*Suite: unstable
	*Codename: ~~amoeba~~		*Codename: alpha
	*Components: main		*Components: main
	*Architectures: i386 armel (all)		*Architectures: i386 armel (all)

	(later we will have a stable distribution, and a similar promotion interface to extras one will be used)		(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 ==		== Upload possibilities ==

imported_>stskeeps at 16:02, 15 December 2008

2008-12-15T16:02:40Z

← Older revision		Revision as of 16:02, 15 December 2008
Line 3:		Line 3:
	== Repository layout ==		== Repository layout ==

	Suite: unstable		*Suite: unstable
	Codename: amoeba		*Codename: amoeba
	Components: main		*Components: main
	Architectures: i386 armel (all)		*Architectures: i386 armel (all)

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

	== Upload possibilities ==		== Upload possibilities ==

imported_>stskeeps: New page: As part of the Mer bootstrapping process, a repository at http://repository.maemo.org/community/ will have to be set up. == Repository layout == Suite: unstable Codename: amoeba Componen...

2008-12-15T15:57:23Z

New page: As part of the Mer bootstrapping process, a repository at http://repository.maemo.org/community/ will have to be set up. == Repository layout == Suite: unstable Codename: amoeba Componen...

New page

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

== Repository layout ==

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

(later we will have a stable distribution)

== 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 ==

*Builders should target both i386 and armel (armv5el, not vfp) (will probably have to be set with CFLAGS)
*Mer has a scratchbox v1 SDK (see [http://wiki.maemo.org/Mer_Blueprint#SB1_SDK_Guide SB1 SDK Guide]), using scratchbox-toolchain-arm-linux-cs2008q3-72_1.0.8-1_i386.deb, and a rootstrap for armel. i386 rootstrap TBA.