view debian/control @ 978:8328337d23b2

docs: add new user guide

This has also been reviewed to death on evolve-testers. There are
still a couple of short sections to write (clearly marked "TODO"), and
one example to add. But (if I may be so bold) this is a gigantic
improvement over the current docs, so it really should get merged.

Incidentally, the figures are all SVG files created with Inkscape.
They're not perfect, but they're pretty nice. Anyone who knows a
better way to create technical diagrams is welcome to contribute.

One wart: there's a test script that accompanies the document and
largely duplicates it, but I haven't unified them. I've been
concentrating on writing the best possible content, not on fiddling
with tools. I suspect that unifying them will be non-trivial, but
definitely worth doing.

Source: mercurial-evolve
Section: vcs
Priority: optional
Maintainer: Logilab <[e-mail]>
Uploaders:
 Julien Cristau <[e-mail]>,
 Pierre-Yves David <[e-mail]>,
Standards-Version: 3.9.3
Build-Depends:
 mercurial (>=2.6~),
 python,
 debhelper (>= 8),
 python-sphinx (>= 1.0.8),
 imagemagick,
 librsvg2-bin,
Python-Version: >= 2.6
Homepage: https://bitbucket.org/marmoute/mutable-history

Package: mercurial-evolve
Architecture: all
Depends:
 ${python:Depends},
 ${misc:Depends},
 mercurial (>= 2.6),
Description: evolve extension for Mercurial
 This package provides the experimental "evolve" extension for the Mercurial
 DVCS.
 .
 This extension provides several commands to mutate history and deal with issues
 it may raise.
 .
 It also:
  - enables the "Changeset Obsolescence" feature of mercurial,
  - alters core command and extension that rewrite history to use this feature,
  - improves some aspects of the early implementation in Mercurial 2.3.
 .
 **These extensions are experimental and are not meant for production.**