These are a number of dirty scripts to maintain Maemo forks of Debian

packages.  They expect the repo layout produced by apt-source and a

changelog.Maemo file.

The basic purpose of these tools is to invisibly add some black magic

to a source package that will turn Scratchbox into a more sane build

environment when the package is build there.  If you build it anywhere

else, the black magic disables itself.

Hopefully, the Maemo SDK will evolve to not need any of this black

magic.  Indeed, you could take the black magic as a sort of todo list

for how to improve the Maemo SDK.

- maemoify-init

Create the initial repo layout and changelog.Maemo.

- maemoify-tag [BRANCH]

Create a tag from BRANCH that will (most likely) build in a standard

Maemo SDK.  The black magic is deployed on the tag to make this

happen, but your branch remains clean.

Tagging means that debian/changelog.Maemo is merged into

debian/changelog, debian/control is updated to reflect the real

Maintainer, Origin, and VCS locations, and debian/rules is modified to

carry out the black magic at build time.

By default, the "maemo" branch is tagged.

- maemoify-tag-native [BRANCH]

Like maemoify-tag, but does not touch debian/changelog or

debian/control, and BRANCH defaults to "master", not "maemo".

- maemoify-rebase

Rebases the Maemo changes on top of a new Debian version.  Because

dark magic is only used during tagging, only 'real' conflicts are

expected, not those caused by gratuitous changes to placate

Scratchbox.

- maemoify-check

Lists all subdirectories that need rebasing or other kinds of

attention.

- maemoify-clean

Cleans all subdirectories by reverting local changes and deleting

untracked files.

- maemoify-patch

Performs the dark magic.  It is used by maemoify-tag and

maemoify-tag-native.