pcp
[Top] [All Lists]

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

To: Lukas Berk <lberk@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Subject: Re: [pcp] [RFC] Minimizing Installation Size for Reduced PCP Footprint
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Tue, 10 Mar 2015 15:26:37 -0400
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <87bnk0wzn5.fsf@xxxxxxxxxx>
References: <87bnk0wzn5.fsf@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
On 03/10/2015 01:06 PM, Lukas Berk wrote:
Hi All,

I was asked to take a look at minimizing the base PCP installation
(RHBZ1182184[1]) and was experimenting with a few aspects of it.  I'd
like to get some feedback before I start more indepth hacking on it.
[ ... ]
Removing direct dependency in libpcp on Avahi:

I took this to mean, add a ./configure --without-avahi option (invokable
via ./Makepkgs) which configures functionality via buildefs.h
accordingly in libpcp.  Nathan, is this what you had in mind?
There is already a ./configure option that covers this, although it is perhaps misnamed as --with[out]-discovery. The current implementation checks for he presence of the needed avahi headers and libraries. There are currently two methods of discovery; avahi and active scanning, the latter of which can't be disabled (and doesn't need that capability). I don't know if the name of this option can be changed at this point (Nathan?), but perhaps a the aptly named synonym that you propose could be added.

I understood this to be a similar item to the NSPR/NSS one. i.e. to implement dynamic loading of the avahi-client library on demand when needed using dlopen(3).

Dave

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