Lukas Berk <lberk@xxxxxxxxxx> writes:
> [...]
> 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. [...]
An option for compiling out avahi support is not what's being called
for.
> Pmwebd dependencies on X11/desktop libraries:
>
> Considering pmwebd is already it's own package, which doesn't have to be
> installed on the collection machines (rather, could be install on the
> sysadmin/developer's machine). I'm not sure if this makes sense to
> persue immediately. [...]
... or at all. Or if this were an actual showstopper, one might
pursue it by reworking the code to use some other graphics-rendering
library instead of Cairo, though that would limit its future
beautification potential.
> Removing the direct dependency in libpcp on NSS/SSL:
> [...]
It seems to me that the above "remove direct dependency" items are
questionable, assuming we're talking about replacing ordinary dynamic
linkage with dlopen() and such. The dependencies don't disappear, but
would merely be hidden from the packaging system. Where a user were
to use the related functionality, she would encounter runtime errors
as dlopen()s fail. We would lose linker and packaging-enforced
version matching. We would lose compile-time type checking on
invoking the dlsym() function pointers.
That's a high cost, just to save some installation footprint.
- FChE
|