Differences between revisions 2 and 3
Revision 2 as of 2010-10-11 09:33:10
Size: 1994
Editor: DidierRaboud
Comment: +fabo's packages
Revision 3 as of 2010-10-11 10:12:43
Size: 2995
Editor: DidierRaboud
Comment: + add OdyX's clean'ed repositories
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:

== Packaging practices ==

Due to the non-reaction of upstream to the [[http://lists.meego.com/pipermail/meego-dev/2010-September/006205.html|[Proposal] Packaging management in DVCS]] mail, most upstream repositories ship packaging files (debian/, *.spec, *.yaml files and directories). In order to workaround this, DidierRaboud runs a "cleaning" script bi-daily that pushes to gitorious too. The master branch of said "cleaned" repository doesn't contain the packaging files and upstream/${version} tags are created with "git changelogs" included. This master branch is regularly (hand-)merged into the "upstream" branch of the alioth git repositories.

Additionally, as the upstream/${version} are git leaves (not in the chain of commits leading to "upstream"), most alioth repositories include a "mergeNewUpstreamRelease.sh" that should be called from the "master" branch as $ debian/mergeNewUpstreamRelease.sh upstream/${version} . This handles the merging and the pristine-tar generation.

Debian meego maintainers

Infrastructure

Interacting with the team

  • Mailing list: <pkg-meego-maintainers AT alioth DOT debian DOT org>

  • Public IRC channel: #debian-meego on irc.debian.org (OFTC)

Packages list

Package

ITP

VCS

Upstream git

Cleaned up git

Uploaders

Comments

libmeegotouch

597295

Git

libmeegotouch

libmeegotouch-clean

DidierRaboud

meego-packaging-tools

592314

Git

meego-packaging-tools

N/A

?FathiBoudra

mic2

578170

Git

image-creator

N/A

?FathiBoudra

meegotouch-theme

599738

Git

meegotouch-theme

meegotouch-theme-clean

DidierRaboud

spectacle

592311

Git

spectacle

N/A

?FathiBoudra

Packaging practices

Due to the non-reaction of upstream to the [Proposal] Packaging management in DVCS mail, most upstream repositories ship packaging files (debian/, *.spec, *.yaml files and directories). In order to workaround this, DidierRaboud runs a "cleaning" script bi-daily that pushes to gitorious too. The master branch of said "cleaned" repository doesn't contain the packaging files and upstream/${version} tags are created with "git changelogs" included. This master branch is regularly (hand-)merged into the "upstream" branch of the alioth git repositories.

Additionally, as the upstream/${version} are git leaves (not in the chain of commits leading to "upstream"), most alioth repositories include a "mergeNewUpstreamRelease.sh" that should be called from the "master" branch as $ debian/mergeNewUpstreamRelease.sh upstream/${version} . This handles the merging and the pristine-tar generation.