On Mon, 29 Mar 2004, Tim Cook wrote:
> The specific issue with TORCH still remains that we disagree because I
> say it is not a technical issue because there is no interaction
> (therefore no conflict) between the Zope packages I put together and any
> others on a Debian system. I just happen to be using open source
> building blocks that are of different version numbers. While your
> viewpoint seems to be that it is difficult to maintain the Zope, Plone,
> other Products that I use as a separate package. I say this is what
> gives me the control and stability that I need to be confident in my
> foundation.
The only thing I could advise here is to make reasonable suggestions
to the (work in progress) Debian Zope policy (you do not necessarily
be subscribed to the zope packagers list to post and can read it via
archive) how you would suggest handling products with different versions.
> I don't have to wait for a new version to be added to the Debian
> distribution nor do I worry that a new version of a product will be
> added that causes a conflict with my application. I don't view TORCH2 as
> a plug-in Zope Product. TORCH2 is a compilation of all that code
> together.
If you ask me I regard it irespecting the points
- stability
- security
- maintainance of bugs (you can not use a bug tracking system)
- upgradability
as a technically questionable approach. When I mentioned this in private
mail you answered (regarding the point about stability): "Stable yes, stale no."
So I know your point but I totally disagree. But as I said - it does not
depend from me in person and if you are able to make reasonable suggestions
to other Debian developers and are able to convince them - just go for it.
(Perhaps I'm wrong and I would love to see Torch2 inside Debian.)
Kind regards
Andreas.
