----- Original Message -----
>
> Hi -
>
> > [...]
> > commit 1d7cbdeb246410ffba4d48570fce21d0b2168484
> > Author: Nathan Scott <nathans@xxxxxxxxxx>
> > Date: Thu Feb 13 14:46:27 2014 +1100
> >
> > Packaging changes to support pcp-manager and pcp-webapi split
> >
> > Migrate pmmgr(1) and pmwebd(1) daemons into their own packages.
> > This allows for independent development on pmmgr and potentially
> > aggressive enablement of new features there,
>
> This is unfortunate.
>
Having made this change, I'm wishing we did it earlier - it's a good
thing. (How many other packages have *7* init scripts and counting?)
Other than helping resolve potential administrative conflicts, it has
clear advantages like being tagged as a more experimental package.
We *could* also choose to enable the daemon by default here at some
point, which we can never do in the base RPM. And its makes good
security sense - people should be able to install a minimal set of
daemons, even if they are off by default - many sysadmins I've come
across just don't want unused daemons there at all where possible.
>
> > as well as removing the (non-default install) libmicrohttpd
> > dependency from the core PCP packages.
>
> Surely disk space concerns don't arise from a 95 kilobyte shared
> library (libmicrohttpd), and a 41 kilobyte binary (pmwebd); surely
> security concerns don't arise as pmwebd should not be started by
> default; so what is the problem?
There have been complaints about pulling in libmicrohttpd, which is
a non-default package. Plus, the too-many-optional-daemons points.
cheers.
--
Nathan
|