On Sun, 28 Mar 2004, Andrew Ho wrote:
> > Either way, I am not upset about TORCH not being included in Debian Med
> > or as an officially blessed Debian package.
>
> A time may come when at least one TORCH user become sufficiently upset -
> and take action to package TORCH for Debian. :-)
Well, there is just one step more in this direction: Tim has just
builded the files which are neessary to build a package.
> Personally, I just have not had time to learn how to build Debian
> packages. (It is probably easier than I imagine.)
It is not very hard to learn. Tim managed it in principle and he would
surely agree with me that it was not really hard. More or less writing
Makefile and some stuff around.
http://sourceforge.net/project/showfiles.php?group_id=70886
The problem is that Tim's upstream TORCH2 product depends from Zope products
which either
- have different version numbers than the packages available in Debian
(this is a problem which will be fixed in the future if Tim decides to
settle down to a stable upstream version of CMF / Plone) or
- do not (yet) exist in Debian. I'd volunteer to help packaging these
but they do not really belong to Torch itself and we should discuss
the advantages and disadvantages of packaging this stuff separately
on debian-devel list instead of OpenHealth (where it is highly of-topic).
> Once I do, I will
> package OIO and all dependent packages that currently do not have Debian
> package available!
I repeat I'm volunteering to integrate all this stuff. As a prove of my
work in this you might have a look at the zope-zms package:
http://packages.debian.org/testing/web/zope-zms
The missing dependencies in Debian were: zope-epoz and zope-textindexng2.
I'm maintaining these packages as well. So it *is* possible to get the
missing dependencies into Debian, but it is *not* possible to include
stuff which conflicts with other packages.
BTW, Andrew, you might ask Tim for reasons why he decided to build Torch2
in the form of Python products. As I told you it will be *much* less effort
to install these without user interaction and this building good quality
Debian packages is much simpler. In this aspect I have enough skills to
build Debian packages from Torch2 but I have no real clue how to build OIO
packages (not that it would be impossible - perhaps Zope 3 will provide
a method to import ZEXP files reliable via script).
Kind regards
Andreas.
