pcp
[Top] [All Lists]

Re: pcp updates: pmdalinux vs valgrind vs s390x, packaging split

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: pcp updates: pmdalinux vs valgrind vs s390x, packaging split
From: fche@xxxxxxxxxx (Frank Ch. Eigler)
Date: Mon, 17 Feb 2014 11:41:16 -0500
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1116704166.6120773.1392277652694.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Thu, 13 Feb 2014 02:47:32 -0500 (EST)")
References: <964461579.6117843.1392277555477.JavaMail.zimbra@xxxxxxxxxx> <1116704166.6120773.1392277652694.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
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.


>     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?


- FChE

<Prev in Thread] Current Thread [Next in Thread>