----- Original Message -----
> On Thu, 7 Nov 2013 16:41:14 -0500 (EST), Nathan Scott wrote:
>
> nathans> The idea is to allow development using pcp libraries, headers,
> nathans> and perly/snakey bits without having to install pcp itself (and
> nathans> hence have to worry about starting daemons and so on).
>
> Ah, I've misunderstood the intent then - I was thinking that you were
> trying to make life easier for the end user like it was done in the
> past by unbundling Infiniband bits from the main package.
There is an element of that too - I'd expect any new PMDAs which add new
dependencies would be handled the same way as pcp-pmda-infiniband. But,
things which are "core" often can't easily be abstracted away - like the
NSS/SSL dependencies. We'd also like to make sure that functionality is
installed and available when people need it, even if they don't realise
during the initial install they might need it (like pmwebd & perl/python
APIs)... so its a judgement call each time I guess.
> I was doing a "demo" of PCP and needed to install it on a VM which
> doesn't have access to yum so getting all the prereqs was major pita.
Yeah, understood - its a tough balancing act between introducing more &
more dependencies with each new feature, versus not having the packages
containing important functionality when people need them. Perhaps we're
favouring the latter too much at the moment - the spec files used to do
the builds are in build/rpm/* so feel free to hack and suggest alternate
package splits for future releases... its certainly not set in stone.
cheers.
--
Nathan
|