[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FreePM.deb design



On Fri, 26 Apr 2002, Tim Cook wrote:

> I will entertain any and all comments on this philosophy but *I*
> think the best thing to do is to build a completely standalone
> FreePM with all the requirements in one package.  The reason is that
> the Zope, Python and Zope Products versions distributed with Debian
> are outside my control.  A difference in version can and probably
> will break something.  It is not always feasible to try and track
> multiple versions of multiple products.  Since FreePM will be a
> major application where it will be used, it may very well be a good
> thing not to mix it with other Zope applications.
I think I understand your point, but it is not your task to
ensure that FreePM works on a Debian system.  This is the task of
the Debian maintainer and he has to care for the requirements.

> The downside is that it will cause you to have two copies of Zope.
> That really shouldn't be an issue though if it is a binary install
> and uses it's own version of the Python interpreter as well. Extra
> disk space required is quite minimal really.
This is not the real downside.  Diskspace is quite cheep compared
to other downsides:

  - Are you able to care for security updates for the Python-Verison you use?
  - Are you able to care for security updates for the Zope-Verison you use?
  - Are you able to care for security updates for all the separate Zope
    products included into your FreePM distribution.

Provided that you are able to do this (well I do not doubt that you
*could* spend the time for this - but it would be of more profit for
FreePM if you would spend your time with developing than with such
stuff).
Debian enables to care for security updates in principle via cron job.
Well, security is not a thing you should do automatically and you
are not advised to do so.  But it works in principle and you can
just check + donwload fixed packages and send an email to the local
admin if there are things to be done for security.  I guess we are
talking about *confident* information ...

  - Will all users of FreePM follow an security issue and update
    their whole system.
  - How much time would they need to care for an update?
  - Are you sure that those updates will be really done?

Where to report bugs inside those software which is not under your
direct control.  Do you want to install a separate bug tracking
system like Debian BTS which cares for all Debian packages?

> The only conflict is the default port numbers which is easily taken
> care of with a FreePM specific start script.
Really no problem here.  Debian Zope just uses a different port from
the default.

> It would also give me
> more control over the entire Zope configuration which can make it
> easier to install FreePM and to troubleshoot problems over the
> mailing list because the default configuration for Zope will be
> known.
This is a topic the Debian maintainer has to care for.

> I will need to take on the responsibility of notifying FreePM users
> of Zope security upgrades etc.
I doubt that you are able to care faster than the process described
above ...

> Comments? What did I miss? <s>
Well, all I said does not speak against the idea to distribute
FreePM as a whole if you like this.  But if I (and I think I'm
speaking for all other Debian developers) should care for Debian
packages we will do it in the Debian style.

Kind regards

         Andreas.


-- 
To UNSUBSCRIBE, email to debian-med-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: