On Wed, Oct 16, 2002 at 07:27:38PM +0200, Stefan Gybas wrote:
>
> Andres Salomon wrote:
>
> >I still plan to continue intermezzo packaging; however, I do not feel it
> >is stable enough for production use.
>
> That's why new packages go to the unstable distribution. For example, a
> CVS snapshot of Samba 3.0 is there - it's also not ready for production
> IMHO.
Samba is usable. It supports the features that it offers. It may have
bugs, but it's at least usable for most of those features. Intermezzo,
on the other hand, does not support any features other than replication,
at the moment; and even that is buggy.
>
> > I do not want to see it packaged until more work is done on it
> (upstream).
>
> Why are there RPM packages then?
Because Peter/Robert use redhat. There's also the historical aspect of
InterSync requiring ghttpd. Normal libghttp didn't install all of what
was needed by InterSync during compilation, so they had to release RPMs
with a modified ghttp. The build system uses the .spec file from the
RPM to get the version/package name, as well; it's simply what the
original authors of Intermezzo preferred to release with.
>
> > Please do not upload 0.9.5 packages.
>
> It will be a long time before sarge is released and if InterMezzo is not
> ready at that time it can simply be postponed for the next release.
I don't see what the rush is right now. If you upload intermezzo
packages, you _will_ have to support users using unstable. There _will_
be longstanding severe/grave bug reports on the package. I would rather
see a quality package put into debian.
>
> My issue is this: I now know how set up InterMezzo (and even better, a
> customer paid me to gain this knowledge). I can now either spend a few
> hours working on InterMezzo packages (so others can try InterMezzo and
> ciontribute to the package and upstream) or I can work on my other
> packages and forget what I have learned about InterMezzo after a few
> weeks. Chose whatever you think is best for Debian and InterMezzo.
You're welcome to do unofficial packages; I would even encourage uploads
to experimental, but not to unstable. As far as the knowledge you have
gained about setting up InterSync; it _will_ change. InterSync does
most of the legwork upon startup (even right down to adding new users to
the system); also, the way it is run will change. There need to be
provisions for security, ways to specify transports (rsync, httpds other
than apache, etc), and many other things. Intermezzo is simply not
ready, and the knowledge you have about it now will be obsolete by the
time it is.
>
> Greetings,
> Stefan Gybas
--
It's not denial. I'm just selective about the reality I accept.
-- Bill Watterson
