<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><div class="">On Jul 3, 2017, at 12:07, Ken Cunningham wrote:</div><div class=""><br class="Apple-interchange-newline"></div><blockquote type="cite" class=""><div class=""><span style="font-family: Menlo-Regular; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">As we have said before (last year) this library could be automatically linked in by base. That would cause trouble with the ports that have already patched in a def, tho.</span></div></blockquote></div><br class=""><div class="">Your library offers multiple functions... getline, strndup, etc.</div><div class=""><br class=""></div><div class="">What happens if a software package provides, for example, a compatibility implementation of getline but not strndup? Can your library be used in this case or will that also "cause trouble", as you put it above?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I see the port and a portgroup have been added to MacPorts. I would like to request that each port that adopts this port/portgroup also add a comment explaining upstream's stance on the issue. For example, a link to the upstream bug report.</div><div class=""><br class=""></div></body></html>