Bugzilla Bug 85998

There's new version of monotone VCS tool. It is totaly incompatibile with
previous  versions (yet again) and need both database reloading (because of
switch to sqlite3) and migrate&rebuild procedure to migrate to support new
epoch feature.
Datails here: http://venge.net/monotone/UPGRADE
Changes here: http://venge.net/monotone/NEWS

Renaming old 0.16 ebuild works well, but there should be STRONG sugestion to
dump user's database(s) to sql file(s) _BEFORE_ upgrade (because of not
supported sqlite2 format in 0.17): "monotone --db=user.db db dump >
user.db.sql" and load them with new merged monotone version to _SEPARATE_ (new)
db file: "monotone --db=user.new.db db load < user.db.sql".

Reproducible: Always
Steps to Reproduce:

Maybe it would be better to assign this release witch new SLOT?

to do a new slot, the filesystem conflicts need to be resolved.

There are two solutions I see:
- remanme monotone binary & related stuff to monotone-0.17
- strong sugestion before merging to read UPGRADE instruction and just upgrade to new version (this is my preferred one)

can you please attach an ebuild using either suggestion. I'm a little pressed
for time.

Created an attachment (id=54238) [details]
new slot version of monotone-0.17

I made ebuild, that should work also for future incompatibile releases. Change
of binary name, which was considered at monotone-devel list is also easy
supportable in future.
I think this version (SLOT one) is more convenient to community that isn't
forced to upgrade. Also upgrade is much easier.

added - thankyou. good ebuild and thanks for putting in a slot version.

Thank you for adding. I forgot to notice that test 62 in testsuite is no longer
problematic, so the warning can be deleted.

Created an attachment (id=56077) [details]
SRC_URI change for 0.18 version

0.18 is out, 0.17 ebuild works well but needs SRC_URI change.

Version bump

version bump added.