Issues with Epoch

[Evan Prodromou <evan@debian.org>]

So, hi. I've got some package-versioning issues, and I wanted to get
some feedback from folks who are smarter than me.

I'm working on the gnustep-guile package. The source package contains
three separate pieces of software: gnustep-guile (a Guile extension to
talk to GNUstep), the ScriptKit (a GNUstep extension for embedding
Guile scripts), and greg (a regression-testing tool for Guile). I
plan on creating 3 binary packages, one for each bit of software.*

Both the ScriptKit and greg used to be distributed separate from
gnustep-guile, and they've got different internal version numbers. But
I think the package version has to be the same for all three binary
packages. I tried making packages with different version numbers, and
although they worked well, the ftp service on master barfed when it
saw them.

SO, I'm going to have all three packages with the same version number,
instead. My problem, though, is that greg used to be distributed as
its own package, and the version number for the old package (1.4) is
higher than the version number for the gnustep-guile package (1.1.4).

I think this calls for an epoch. However, I'm a little wary of this,
since the other two packages will have to have an epoch, too
(viz. problems with having different version numbers).

Any advice? Is this a sane plan?

~ESP

* Actually, more than 3 -- there's debug, devel libs, docs, etc. But
  let's say 3 for now.

-- 
Evan Prodromou
evan@debian.org