[csw-pkgsubmissions] /newpkgs amanda

[Philip Brown]

On Thu, May 6, 2010 at 6:39 AM, Darin Perusich
<Darin.Perusich at cognigencorp.com> wrote:
> Hi Phil,
>
> New amanda packages are in newpkgs for deployment.

hi again Darin,

I'm tying multiple threads together, by copying this to the
"pkgsubmissions" mailing list.
The issues involved, were discussed on the maintainers list, with subject
"cswinetd and cswetcservices?"
(We also exchanged a few emails privately, after that discussion)

Darin, I'm afraid that I'm not going to allow in your latest amanda
packages for the following reasons. The summary being, that it goes
against core principles of,
"To provide a straightforward, easy-to-use experience for the user".

You have chosen to deliver it in a way that makes the user
unnecessarily jump through more hoops, if they do want it installed
and running.

While I completely understand your perspective of "off by default, is
better/more secure"...
that is a choice for you to make for boxes that *you* administer. You
should not be imposing your choice on all of our users, if their
choice is the opposite. We need to respect our users enough to allow
them to make their own choices in the matter.

Right now, we have a straightforward, easy to use, *same for
everyone*, framework, that allows our users to individually choose
whether they want services to automatically be enabled at pkgadd time,
or disabled.  Please use it.

>From your posting on the maintainers list, it seems that you have
already done the work to convert the package to use our standard
csw----- classes.
So this is not even a matter of asking you to do "more" work; only to
simply release what you have already done in that regard.


The argument of "well this is how it acted previously", is not enough
to allow them through. If that were enough, then we would never make
significant improvements to our packages.

if for some reason you decide to stick with postinstall scripts
instead of our easy to use, standardized class action scripts, that is
fine... but you will then need to do the extra work of making your
postinstall scripts respect the autoenable_demons setting in csw.conf
Also recognizing our documented standards, that if that setting is not
present, it is understood to be defaulted to "yes, enable them".