<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 21 May 2007, at 10:36 PM, Ken Rickard wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><BR>Include a section in the Project description that lets the developer place links to the supported third-party libraries hosted on external sites. These would be similar to the CVS / Documentation link fields that we have now.<SPAN class="Apple-converted-space"> </SPAN><BR><BR></SPAN></BLOCKQUOTE></DIV>how about you define it in the .info, and drupal.org processes it from there.<BR><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This way we could also build a package building script that can automate making gzips containing the info.</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>