Andres Salomon wrote:
There _will_ be longstanding severe/grave bug reports on the package.
That't fine. This way it will be kept out of testing.
I'd rather have a package with some bugs that I can use in some fields
than no package at all. If you don't want to use the package simply
don't install it.
> it _will_ change.
Ok, then I'll change the package accordingly. It won't the first
changing package that I'm maintainig. You can take a look at Tomcat's
history for example: Tomcat 4.1.2 has almost nothing in common with the
first Tomcat 3.x package.
> InterSync does most of the legwork upon startup (even right down to
> adding new users to the system);
I know this and I'll patch intersync to suit the Debian Policy. I'll
disable the automatic startup of httpd and leave it up to the user to
configure their web server to restrict access (allow, deny, SSL, ...) to
InterMezzo's CGIs.
I'd rather have you maintain the packages since you probably know more
about InterMezzo than me. But then you have to upload your packages
within the next few weeks. Keeping an ITP open for almost 2 years is not
an option.
Greetings,
Stefan Gybas
