Release Jed 0.99.18-1

[Rafael Laboissiere]

* G. Milde <g.milde at web.de> [2006-05-16 13:43]:

>        BTW: What is the difference of README.debian vs.
>             jed-common.README.Debian?

This is a real problem, thanks for spotting it.  It seems that only
jed-common.README.Debian is installed as /usr/share/doc/jed/README.Debian
and that README.Debian is never installed.  This happens because
/usr/share/doc/jed is a symlink to /usr/share/doc/jed-common.  Jürgen,
could you please look at this.

Since jed is the first binary package described in debian/control, the
README.Debian file is installed as /usr/share/doc/jed/README.Debian.  The
jed-common.README.Debian is installed by dh_installdocs as
/usr/share/doc/jed-common/README.Debian which, due to the symlink is the
same as /usr/share/doc/jed/README.Debian.

At any rate, we must update the text in README.Debian, which refers to
version 0.99-17 of JED.

> >    * Cope with the jedstate package, which will be become useless with the
> >      new jed pacakge
> 
>        Could we just replace|conflict?

Yes, this is what I thought.  There is now the gdbmrecent package that
can provide the same functionality of jedstate.  Unfortunately,
gdbmrecent it is not a drop-in replacement for jedstate.  With the upload
of 0.99.18 to experimental, users of jedstate (me included) will have
problems.

We might provide a script to convert the ~/.jedstate.db file into the
~/.recent_db file of gdbmrecent.  That should not be too complicated, since
both have the same type:

$ file ~/.recent_db ~/.jedstate.db
/home/rafael/.recent_db:       GNU dbm 1.x or ndbm database, little endian
/home/rafael/.jedstate.db:     GNU dbm 1.x or ndbm database, little endian

-- 
Rafael