On Sat, Jul 16, 2016 at 01:51:37PM +0100, Simon Hobson wrote: > Now, if the devs/maintainers used a "if it's there call it, if it > isn't then don't" approach then I could see that working. I assume > that is a possible way of calling library functions given the number > of programs with optional dependencies/features.
Can anyone explain how to do this? It sounds like a useful technique. -- hendrik _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
