pcp
[Top] [All Lists]

Re: [pcp] [RFC] Minimizing Installation Size for Reduced PCP Footprint

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] [RFC] Minimizing Installation Size for Reduced PCP Footprint
From: Lukas Berk <lberk@xxxxxxxxxx>
Date: Wed, 29 Apr 2015 13:23:03 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <2089951493.8763144.1430262734221.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Tue, 28 Apr 2015 19:12:14 -0400 (EDT)")
References: <87bnk0wzn5.fsf@xxxxxxxxxx> <877ft59dmo.fsf@xxxxxxxxxx> <1344838118.4507317.1429675359315.JavaMail.zimbra@xxxxxxxxxx> <87pp6n7u7g.fsf@xxxxxxxxxx> <2089951493.8763144.1430262734221.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
Hey,

Nathan Scott <nathans@xxxxxxxxxx> writes:
>> I've been toying with this idea a bit, and ended going with the two
>> packages (pcp-collection and pcp-monitor, respectively).  If one is
> Could we use the term "collector" rather than "collection"?  See e.g.
> PCPIntro(1) - 3rd and 4th paragraphs there - that terminology is used
> fairly extensively throughout the Users+Admins Guide book as well.

Ah, I mistyped that, it is already pcp-collector (not collection).

>> interested in installing every pcp package, wildcarding "pcp-*" will
>> work.
> Neat - always the exceptions to the rule though I guess, with python* &
> perl* module package naming conventions.

Yes, but those should get pulled in via package dependencies anyways, no?
At least with the pcp-pmda* packages I've create, they require the
proper perl/python pmda bindings.

Cheers,

Lukas

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